Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Transaction Log Backup Failures Expand / Collapse
Author
Message
Posted Thursday, May 22, 2008 2:53 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 3:33 PM
Points: 356, Visits: 1,991
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.
Post #505493
Posted Thursday, May 22, 2008 6:03 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, April 14, 2014 6:37 PM
Points: 69, Visits: 213
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.
Post #505564
Posted Friday, May 24, 2013 10:44 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, August 30, 2013 8:49 AM
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.
Post #1456620
Posted Friday, May 24, 2013 1:28 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 11:11 PM
Points: 35,769, Visits: 32,432
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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1456673
Posted Friday, May 24, 2013 1:31 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 11:11 PM
Points: 35,769, Visits: 32,432
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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1456674
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse