October 30, 2012 at 7:32 pm
I have full backup scheduled daily at evening 5 PM.
Differential occurs daily after every 3 hours throughout the day.
Log backups are scheduled after every 15 minutes.
But the scheduled after 2 am till 3 am for log backup starts failing stating the following error:
"BACKUP LOG cannot be performed because there is no current database backup.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
October 30, 2012 at 9:01 pm
I got it there is job which runs at 1:45 which truncates the log and so the log backup starts failing and it resumes once differential is completed at 3:00 am after 3 am log backup are successfull.
October 30, 2012 at 10:39 pm
This was removed by the editor as SPAM
October 31, 2012 at 1:54 am
mahesh.dasoni (10/30/2012)
I got it there is job which runs at 1:45 which truncates the log and so the log backup starts failing and it resumes once differential is completed at 3:00 am after 3 am log backup are successfull.
Don't manually truncate your log. You're breaking your log chain and reducing the options you have for restoring that DB in the case of a disaster.
Please read through this - Managing Transaction Logs[/url]
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 31, 2012 at 6:14 am
you have scheduled transactional log backup then why there is job for truncate log file :blink:
-----------------------------------------------------------------------------
संकेत कोकणे
November 9, 2012 at 3:33 am
sanket kokane (10/31/2012)
you have scheduled transactional log backup then why there is job for truncate log file :blink:
+1
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
December 12, 2012 at 12:59 am
hi mahesh,
This error occurs when someone has run a process that has broken the log chain. Probably ran the command BACKUP LOG [Jul_Reports] WITH TRUNCATE_ONLY, or the database was switched to SIMPLE recovery and then back to FULL.
if someone using backup log with truncate_only command in their job
please set below trace flag
3031
3231
it wont break lsn chain of database.
you will get explaination for traceflag on google.
December 12, 2012 at 2:30 am
Hemant.R (12/12/2012)
hi mahesh,This error occurs when someone has run a process that has broken the log chain. Probably ran the command BACKUP LOG [Jul_Reports] WITH TRUNCATE_ONLY, or the database was switched to SIMPLE recovery and then back to FULL.
if someone using backup log with truncate_only command in their job
please set below trace flag
3031
3231
it wont break lsn chain of database.
you will get explaination for traceflag on google.
A month old post :hehe:
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply