09-28-2012 08:31 AM
I recently setup a differential backup job for a MS SQL (SQL 2008 standard) database, but I'm having trouble getting it working. The diff. job works only once; after a full DB backup. Every other time it runs I get the following error:
Error Code: E0000363
The job failed with the following error: The Backup Exec SQL Agent was not used to create the last full, differential, or log backup for this database. You must use the SQL Agent to run a full backup before you can run a differential backup or transaction log backup.
For additional information regarding this error refer to link V-79-57344-867
Using the SQL Management Studio Tools I ran the suggested SQL query to see if any other backup jobs were running. The result for every database I picked was the same: Backup Exec SQL Server Agent. Not sure what else I can try to resolve this problem. Feedback much appreciated.
Below is how I setup my differential Microsoft SQL DB backup jobs.
Weekly Full
Daily Differential
Daily Log Backup (after differential)
09-28-2012 08:53 AM
Thundercleese,
Give these two documents a look over.
http://www.symantec.com/business/support/index?page=content&id=TECH58674
http://www.symantec.com/business/support/index?page=content&id=TECH137587
09-28-2012 09:02 AM
The Incremental backups running after Differential are causing the failure. Choose either of the backup methods.
09-28-2012 09:44 AM
I already tried the solution in the first link, but unfortunately the only result I get from the query is: Backup Exec SQL Server Agent. I doubled check, and my full DB backup job is set to Back up database or file group changes only.
The second link doesn't apply to my environment. The MS SQL DB is running on a physical server box (no virtualization).
Thanks for the documents.
09-28-2012 09:44 AM
I don't have any incremental backup jobs for the DB. More correctly I've disabled them all while attempting to get this differential backup solution to work.
09-28-2012 11:22 AM
Do you have just the one SQL backup job scheduled for that server. "Full". Having more than one full SQL backup even if created by B.E. may cause an issue.
For example
SQL full - a Successful
SQL diff - a successful
SQL full - b successful
SQL diff - b successful
SQL diff - a fail due SQL full b running between this job and last full for SQL A
would you be able to provide the results of the query ... Blocking any sensitive information "server names"
09-28-2012 12:38 PM
Hi Thundercleese, is there any scheduled SQL database maintenance running?
Lenora
09-28-2012 12:42 PM
Yes, I have one backup job for the entire database (total of 186GB).
Example of the MS SQL DB job's run:
MS SQL FULL - Successful
MS SQL DIFF - Successful
MS SQL LOG - Successful
Next day:
MS SQL DIFF - Failed; error E0000363
MS SQL LOG - Successful
....
09-28-2012 01:16 PM
Ok Thunder,
I think that i know whats going on... i believe that the incremental/log backup between the first diff and the second are whats is causing the issue. The log back up is flushing the transaction logs so when the diff attempts to run it does not see what it is expecting. would it be possible to schedule your log backups to preceed the full.
possible
MS SQL FULL
MS SQL DIF
next day------
MS SQL LOG
MS SQL FULL
MS SQL DIFF
next day ---
MS SQL LOG
MS SQL FULL
MS SQL DIFF
09-28-2012 01:44 PM
Interesting, I never would have thought that the log back up might be flushing the transaction logs. I could setup a backup job like you suggested, but if I'm doing daily MS SQL FULL there wouldn't be a reason for the differential, right? Probably bad practice, but I wonder if things would work if I ran a LOG backup before the weekly FULL? Something like:
weekend
MS SQL LOG
MS SQL FULL
weekday
MS SQL DIFF
MS SQL DIFF
MS SQL DIFF
MS SQL DIFF
MS SQL DIFF
...
09-28-2012 01:52 PM
No, there does not appear to be any scheduled SQL database maintenance running.
How I checked, using Microsoft SQL Server Management Studio:
09-28-2012 06:28 PM
Backing up the transaction logs and truncating them will not affect the sequence. You should not truncate your log before a backup. If you do and your database backup fails, you would not be able to do a point-in-time restore beyond the last database backup. Always truncate your logs AFTER a backup, not before.
If you do not have any other database maintenance going on and the LSN is correct, I would suggest that you start a support case with Symantec for them to take a look at the problem.
10-01-2012 07:23 AM
Your suggested backup schedule should work fine. Please update us after a few backups run
10-24-2012 09:19 AM
The differential backup job will run fine for a few days after a full DB backup, but then it will start to 'error out (E0000363)'. Very odd...
10-25-2012 02:26 PM
Hi,
Have you reviewed the Windows events on the SQL server and the Media Server for errors that maybe occurring during the time of the backup job? This might identify if any other applications are getting in the way of the backup.
Also, do you have any Antivirus programs running? Here is a link for a How To on making exceptions. It refers to thoroughput and SEP but can give a general over view of other programs/problems too. http://www.symantec.com/business/support/index?page=content&id=TECH168940