June 30, 2017 at 7:46 am
I have 5 DBs on one of my prod server and I take log backup every hour (I have setup jobs through maintenance plan). I keep getting emails about failed status but when I check for the error, all the log backups exist on the backup drive. For example
"Executing query "BACKUP LOG [FJMCustomerData] TO DISK = N'G:\SQL_B...".: 100% complete End Progress Progress: 2017-06-30 08:00:03.16 Source: Back Up Database (Transaction Log)"
but in the end, I get this
"End Progress DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:00:00 AM Finished: 8:00:03 AM Elapsed: 2.969 seconds. The package execution failed. The step failed." Any advice on what to look for here?
June 30, 2017 at 8:59 am
newdba2017 - Friday, June 30, 2017 7:46 AMI have 5 DBs on one of my prod server and I take log backup every hour (I have setup jobs through maintenance plan). I keep getting emails about failed status but when I check for the error, all the log backups exist on the backup drive. For example"Executing query "BACKUP LOG [FJMCustomerData] TO DISK = N'G:\SQL_B...".: 100% complete End Progress Progress: 2017-06-30 08:00:03.16 Source: Back Up Database (Transaction Log)"
but in the end, I get this
"End Progress DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:00:00 AM Finished: 8:00:03 AM Elapsed: 2.969 seconds. The package execution failed. The step failed."
Any advice on what to look for here?
A couple of things to check that could be failing after the backup:
Did you check the Reporting and Logging option? Do you have it setup to log the results to a file?
Are there any other tasks after the backup - Maintenance Clean Up task?
Sue
July 3, 2017 at 9:11 am
I've seen that error when it was unable to delete the previous backup file too. I would check to see if you have some really old backup files sitting in your backup folder. If so, and you no longer need them, I'd remove the old ones manually and see if that helps. It did help us when I saw that error.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
July 6, 2017 at 7:30 am
Also look at the size of the backupset table(s) in MSDB....if that old data isn't getting purged it can cause the new info about backups to fail to write to the system tables, even though the backups themselves work just fine.
------------------------------------------------------------------------------------------------Standing in the gap between Consultant and ContractorKevin3NFDallasDBAs.com/BlogWhy is my SQL Log File HUGE?!?![/url]The future of the DBA role...[/url]SQL Security Model in Plain English[/url]
July 7, 2017 at 1:03 am
I would drop the Database Maintenance Plan and recreate it. I have seen this many times before DMPS are prone to this. You can spend hours trying to figure out the logic of why it is not working and create something exactly the same within minutes that works.
I would not use DMPS for this reason and go to a T-SQL based backup solution . Lots of scripts out there Like OLA HALENGRENS.
DMPs just break or flag errors for no apparent reason.
July 7, 2017 at 1:21 am
#or create something exactly the same within minutes that works
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply