November 22, 2010 at 3:54 am
Thank you very much all!
Finally I have restored the databases from some old backups and able to resolve the issue. The server is internal production server so we manage to convince the users.
And the junior DBA has been wraned hope he will not repeat the mistake 🙂
November 22, 2010 at 6:07 am
Excellent. One thing left to do.
GilaMonster (11/19/2010)
In addition, do some diagnoses on that IO subsystem. Something is not right and, unless you find and fix the root cause, this (excluding the missing backups) could happen again.
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
November 23, 2010 at 10:06 am
Sqlsavy (11/19/2010)
Unfortunately a junior DBA who got access to the server disabled the backup for some reason and forgot to enable....
When I have a job that I want disabled for a period of time. instead of disabling it, I often change the start date to a future date, so that it will automatically start running again.
EDIT: Added quote for clarity.
November 23, 2010 at 10:09 am
homebrew01 (11/23/2010)
When I have a job that I want disabled for a period of time. instead of disabling it, I often change the start date to a future date, so that it will automatically start running again.
Did you perhaps post in the wrong thread?
November 23, 2010 at 10:29 am
Brandie Tarvin (11/23/2010)
homebrew01 (11/23/2010)
When I have a job that I want disabled for a period of time. instead of disabling it, I often change the start date to a future date, so that it will automatically start running again.Did you perhaps post in the wrong thread?
I think he's commenting on the junior DBA who disabled the backup job, resulting in there being no backup when the DB went suspect.
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
November 23, 2010 at 10:56 am
GilaMonster (11/23/2010)
Brandie Tarvin (11/23/2010)
homebrew01 (11/23/2010)
When I have a job that I want disabled for a period of time. instead of disabling it, I often change the start date to a future date, so that it will automatically start running again.Did you perhaps post in the wrong thread?
I think he's commenting on the junior DBA who disabled the backup job, resulting in there being no backup when the DB went suspect.
I agree with Gail.
I used that tactic also. That way I don't have to remember to re-enable the job(s).
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
November 23, 2010 at 11:32 am
Along with my missing backups alert, I also get a list of all disabled jobs, including the last time they were run. It also includes scheduled jobs that didn't run on their last schedule, and so on.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 23, 2010 at 12:03 pm
GSquared (11/23/2010)
Along with my missing backups alert, I also get a list of all disabled jobs, including the last time they were run. It also includes scheduled jobs that didn't run on their last schedule, and so on.
Those should be standard reports.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
November 23, 2010 at 12:26 pm
GSquared (11/23/2010)
Along with my missing backups alert, I also get a list of all disabled jobs, including the last time they were run. It also includes scheduled jobs that didn't run on their last schedule, and so on.
I was with you until that comment. What's your technique for figuring that out? Reversing the actual scheduling table against the last start time?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 23, 2010 at 1:02 pm
Craig Farrell (11/23/2010)
GSquared (11/23/2010)
Along with my missing backups alert, I also get a list of all disabled jobs, including the last time they were run. It also includes scheduled jobs that didn't run on their last schedule, and so on.I was with you until that comment. What's your technique for figuring that out? Reversing the actual scheduling table against the last start time?
Yep. I reverse engineer the schedule data in msdb. The job runs daily, so I have it generate a list of the times a job should have run in the last 24 hours, and a list of the days it should have run in the last week, and compare that to the history data for the job.
It's mainly meant to cover "the server/service wasn't up last night when the backups were supposed to run" type scenarios. If the job is scheduled for midnight, and the SQL Agent service isn't running from 1 second before till 1 second after, the job won't start, but won't report as failed either.
It has also come in useful when a job overran its next scheduled start a few times. Detects that quite easily.
If you want, I'll put the whole thing into article form and give it to Steve. Probably should have done that a year ago, when I got it working.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
November 23, 2010 at 1:54 pm
GSquared (11/23/2010)
If you want, I'll put the whole thing into article form and give it to Steve. Probably should have done that a year ago, when I got it working.
Certainly couldn't hurt. I've had to deal with overruns a few times and that'd be nice to detect. The backup protection wouldn't hurt, either. I was hoping though you'd figured out a better way than I had deduced.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
November 23, 2010 at 1:57 pm
Craig Farrell (11/23/2010)
GSquared (11/23/2010)
If you want, I'll put the whole thing into article form and give it to Steve. Probably should have done that a year ago, when I got it working.Certainly couldn't hurt. I've had to deal with overruns a few times and that'd be nice to detect. The backup protection wouldn't hurt, either. I was hoping though you'd figured out a better way than I had deduced.
That would be a good topic for an article. Something that would be nice to add would be detecting long running/stuck jobs.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
November 23, 2010 at 2:02 pm
WayneS (11/23/2010)
Craig Farrell (11/23/2010)
GSquared (11/23/2010)
If you want, I'll put the whole thing into article form and give it to Steve. Probably should have done that a year ago, when I got it working.Certainly couldn't hurt. I've had to deal with overruns a few times and that'd be nice to detect. The backup protection wouldn't hurt, either. I was hoping though you'd figured out a better way than I had deduced.
That would be a good topic for an article. Something that would be nice to add would be detecting long running/stuck jobs.
Easy enough to do.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 13 posts - 16 through 27 (of 27 total)
You must be logged in to reply to this topic. Login to reply