May 2, 2011 at 9:21 pm
Comments posted to this topic are about the item Disaster Recovery Planning
May 3, 2011 at 3:09 am
69% getting this one right. There's a whole Wikipedia article about RTO:
May 3, 2011 at 3:20 am
Thanks for the question
M&M
May 3, 2011 at 6:46 am
Another TLA to remember. 🙂
May 3, 2011 at 7:42 am
Good question.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
May 3, 2011 at 8:19 am
According to Pierre Dorion at TechTarget.com - The RTO, as its full name implies, is a goal or an ideal time in which you need a specific function or service to be available following an interruption. In essence, the RTO represents the maximum amount of time before an organization is negatively impacted by the interruption of one its core business processes or functions.
In that case I would argue that an organization is negatively impacted when they can't log in.
I hope I pasted the quote here properly. Don't want to use info improperly.
May 3, 2011 at 12:26 pm
Oh I was tempted by the 4th choice thinking it might be a trick question 🙂
Great question! I bet you would find disagreement inside many organizations...
Peter Trast
Microsoft Certified ...(insert many literal strings here)
Microsoft Design Architect with Alexander Open Systems
May 3, 2011 at 12:26 pm
Nice question, thanks!
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 3, 2011 at 2:46 pm
Nice question thanks. (Though I am surprised by the number of people getting it correct.)
May 3, 2011 at 4:26 pm
JP Dakota (5/3/2011)
According to Pierre Dorion at TechTarget.com - The RTO, as its full name implies, is a goal or an ideal time in which you need a specific function or service to be available following an interruption. In essence, the RTO represents the maximum amount of time before an organization is negatively impacted by the interruption of one its core business processes or functions.In that case I would argue that an organization is negatively impacted when they can't log in.
I hope I pasted the quote here properly. Don't want to use info improperly.
I don't know that Tech Target is more authoritative than any other source, but RTO can be defined differently in different situations. The important thing is that you develop this into your SLA and are aware of how your customers/management view the RTO requirements in a DR situation.
May 3, 2011 at 7:06 pm
Good question today. It may be a future QOD, and if so, here's a hint. The first option (the last time for which you have useable data) is the RPO, or recovery Point objective. For example, with mirrored databases, you plan for a zero or near-zero RPO (zero data loss). With log shipping every ten minutes to a remote server, you plan for up to a ten minutes RPO. It's easy to confuse the acronyms, but these are pretty much standard terms now.
May 3, 2011 at 11:22 pm
Grrr...answered incorrectly (4th option) and am quite annoyed about it atm.
I was under impression that both options 3 and 4 could be correct.
Is this straightforward thing that RTO applies to the DB layer only?
May 4, 2011 at 7:16 am
RTO applies to the system, and it could be defined in various ways. However #4 doesn't say all clients or every client. An outage could easily be unevenly distributed. A little tricky, and perhaps I should have worded that differently.
Typically the IT guys must get the system working, however they can't necessarily control when a client tries to connect. So your RTO is the time when the system is working and available for connections.
May 4, 2011 at 7:44 am
Good question..
May 5, 2011 at 7:41 pm
This is really a good question.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply