Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Log backup Fails


Log backup Fails

Author
Message
mahesh.dasoni
mahesh.dasoni
SSC Journeyman
SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)

Group: General Forum Members
Points: 85 Visits: 1025
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.
mahesh.dasoni
mahesh.dasoni
SSC Journeyman
SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)SSC Journeyman (85 reputation)

Group: General Forum Members
Points: 85 Visits: 1025
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.
prettsons
prettsons
SSC-Enthusiastic
SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)

Group: General Forum Members
Points: 198 Visits: 1381
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.

Once the log chain is broken, you cannot perform transaction log backups until the log chain has been re-established. To do that, you need to perform either a full or diff backup on that database.

If you don't need the database in full recovery, switch to simple and stop performing transaction log backups.

SQL Database Recovery Expert :-)
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47417 Visits: 44405
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


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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


sanket kokane
sanket kokane
Old Hand
Old Hand (331 reputation)Old Hand (331 reputation)Old Hand (331 reputation)Old Hand (331 reputation)Old Hand (331 reputation)Old Hand (331 reputation)Old Hand (331 reputation)Old Hand (331 reputation)

Group: General Forum Members
Points: 331 Visits: 1019
you have scheduled transactional log backup then why there is job for truncate log file Blink

-----------------------------------------------------------------------------
संकेत कोकणे
Bhuvnesh
Bhuvnesh
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2930 Visits: 4076
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;-)
Hemant.R
Hemant.R
SSC Rookie
SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)SSC Rookie (48 reputation)

Group: General Forum Members
Points: 48 Visits: 240
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.
Bhuvnesh
Bhuvnesh
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2930 Visits: 4076
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;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search