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


Transaction Log Backup Failures


Transaction Log Backup Failures

Author
Message
Ross McMicken
Ross McMicken
Old Hand
Old Hand (388 reputation)Old Hand (388 reputation)Old Hand (388 reputation)Old Hand (388 reputation)Old Hand (388 reputation)Old Hand (388 reputation)Old Hand (388 reputation)Old Hand (388 reputation)

Group: General Forum Members
Points: 388 Visits: 2195
A question came up today on log backup failures. We run log backups hourly. On occasion, the backups fail (no one has sent me a copy of the failure reason). If a log backup fails, does the next log backup capture the missed hour, or is that one lost? Does anyone have a reference in BOL or MS? I haven't found a reference yet.
zombi
zombi
Valued Member
Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)

Group: General Forum Members
Points: 73 Visits: 216
have you set up a differential backup, if not, then this is the time just set it up so even if ur transaction log back up fails u just have a differential back up.

And why don't u create a job alter for ur self so no one has to tell anything to u , if something fails then u will be notified by mail.
mdm72
mdm72
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 56
If I may add a sub-question...

We backup our tlogs every 20 minutes, when the job fails (reason unimportant) we are notified via email/txt. Has anyone executed a scripted job to notify after a second failed job rather than the initial failure? Being that we backup every 20 minutes, we generally watch to see if the next backup succeeds and if so all is well, so to speak.
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45248 Visits: 39932
zombi (5/22/2008)
have you set up a differential backup, if not, then this is the time just set it up so even if ur transaction log back up fails u just have a differential back up.

And why don't u create a job alter for ur self so no one has to tell anything to u , if something fails then u will be notified by mail.


I realize this response if 5 years old but there's no need for a differential backup just because of a single hourly log backup failure. The successful log backup after such a failure will contain all of the information for both hours.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45248 Visits: 39932
mdm72 (5/24/2013)
If I may add a sub-question...

We backup our tlogs every 20 minutes, when the job fails (reason unimportant) we are notified via email/txt. Has anyone executed a scripted job to notify after a second failed job rather than the initial failure? Being that we backup every 20 minutes, we generally watch to see if the next backup succeeds and if so all is well, so to speak.


Is it actually worth trying to do such a thing? You do get notified twice within 20 minutes and, personally, I want to be notified of all such failures. I check the reason on the first failure because it's not always something that will all then next cycle to be successful.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
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