June 17, 2009 at 7:22 am
I was wondering if any one had a Recovery Template that outlines the basic information needed in recovering SQL and the DB's and a way to outline it in a document.
The hardest part for me is coming up with a Document outline that make sense to someone...:-D
Thanks
June 17, 2009 at 7:58 am
Are you asking for documentation on a recovery strategy, or for code?
- 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
June 17, 2009 at 11:23 am
Just looking for a document that outlines common steps for recovery either for the SQL Server or SQL Instance or the Databases. Something along the lines of what is needed for a recovery plan that some of you may have had to come up with.
It would just be nice se see some other documents to make sure I cover all the bases in mine that I need to come up with.
Thanks
June 17, 2009 at 11:45 am
I don't really have a template or written policy. Recovery is generally going to be dependent on what makes it necessary in the first place.
Some of my databases can handle recovering from the daily backup without worrying about point-in-time, because all they have in them is nightly data loads, nothing during the day. Others need up-to-the-second protection, because of routine inserts/updates throughout the day. But even with that in mind, any policy on recovering them would have to be situational.
For example, if a SAN caught on fire and was destroyed, my recovery plan would be very different than if CHECKDB found data corruption in one database. Neither of those would match my recovery plan if I found that someone had hacked the server and truncated all the tables in all the databases. And so on.
So, my policy/template is pretty much, "do what's necessary based on what's causing the situation".
Is that what you're talking about?
- 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
June 17, 2009 at 1:53 pm
That's pretty much what I 'm looking for. Some people put that in a nice formatted document. I would like to see some so that I can get an idea how to form mine.
I would like to format a document that ranges from a single database recovery, to the servers, all the way to the data center being lost. And the document will be written some what detailed in the event they lost me. I have most documention scattered between multilple documents but I thought there may be some nicer formats that other have used that I could adapt my documetation to.
It seems maybe everyone does it like me. 😀
June 18, 2009 at 7:27 am
I would guess that companies where disaster recovery and business continuity are more critical probably have more formal procedures. For example, I would certainly hope that a hospital has all kinds of levels of continuity planning, including recovery plans for all kinds of contingencies on the databases, since that might mean the difference between large numbers of people dying or not. Same for military installations.
For the company's I've worked for, DR/BC are secondary concerns, and that level of formal documentation wouldn't actually have a real value compared to the effort of creating it.
- 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 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply