darrenm Posted July 1, 2013 Share Posted July 1, 2013 RTO is return to operation. It's the time it takes between a failure and everything working again. RPO is recovery point objective. It's the time you can go without losing data. Both standard accepted terms in business continuity. 1 Link to comment Share on other sites More sharing options...
drat01 Posted July 1, 2013 Share Posted July 1, 2013 (edited) RTO is return to operation. It's the time it takes between a failure and everything working again. RPO is recovery point objective. It's the time you can go without losing data. Both standard accepted terms in business continuity. There is often some debate as to exact meaning of the phrases. Within a lot of Business Continuity sector RTO is often defined as Recovery Time Objective (which in reality is what you have said - so I think of both as being very valid) and RPO is Recovery Point Objective. Both are standard metrics and terms that are used in Business Continuity and should always be considered for any data Not considering either can be one of the biggest blunders ever in IT - in my opinion of course Edited July 1, 2013 by drat01 Link to comment Share on other sites More sharing options...
tonyh29 Posted July 1, 2013 Share Posted July 1, 2013 RTO is return to operation. It's the time it takes between a failure and everything working again. RPO is recovery point objective. It's the time you can go without losing data. Both standard accepted terms in business continuity. There is often some debate as to exact meaning of the phrases. Within a lot of Business Continuity sector RTO is often defined as Recovery Time Objective (which in reality is what you have said - so I think of both as being very valid) and RPO is Recovery Point Objective. Both are standard metrics and terms that are used in Business Continuity and should always be considered for any data meh RPO will always be Royal Philharmonic Orchestra 1 Link to comment Share on other sites More sharing options...
islingtonclaret Posted July 1, 2013 Share Posted July 1, 2013 Well that's just cleared up my plain english post then. "the time it takes between a failure and everything working again" is what I would use in that context. The very fact that in Business Continuity the term RPO can be confused with RTO illustrates my point - which was that gobbledigookbusinessdrivel should be avoided where possible. 1 Link to comment Share on other sites More sharing options...
Popular Post colhint Posted July 1, 2013 Popular Post Share Posted July 1, 2013 used to have a Saturday job in a Supermarket. I worked on the fruit and veg. Saturday afternoon early evening me and another lad, our job was to clean everything down while still weighing up customers stuff. This was the days before Sunday opening. Anyway some customer wanted half a melon, but we had none left, although we had plenty of whole Melons. This was a bit of a pain as we'd already cleaned down the prep room. Just then the manager appeared as my mate was trying to talk this customer out of it. He spied the manager some 20 feet away. He nipped over to him and said Some clearing in the woods wants half a melon. He didn't know the Lady had followed him and was stood right at his side. He looked in horror when he saw her, then quick as a flash said, and this lady would like the other half. 6 Link to comment Share on other sites More sharing options...
8pints Posted July 1, 2013 Share Posted July 1, 2013 (edited) then quick as a flash said, and this lady would like the other half. For his quick wit and for you telling the tale today Edited July 1, 2013 by 8pints 1 Link to comment Share on other sites More sharing options...
leviramsey Posted July 1, 2013 VT Supporter Share Posted July 1, 2013 In my last job I was the DBA for a 4TB database of a rolling last 30 days of 6 million insurance quotes a day (it was the back end web service for all the price comparison sites to get their quotes from). It was a circular replicated master-master cluster so any queries other than selects will get run the same on the other server. There was some corruption in one of the nodes' copy of the database so I had the bright idea to just direct all traffic to the good node and run a mysqldump on the bad node pulling good data from the good node. The first bit a mysqldump does is DROP TABLE.. which then gets replicated to the other node.. Database screwed while 300 quotes a second are coming in. Worst bit was there was no backup as the RTO is so long as to be unworkable. So no one could retrieve any quotes from any of the places like confused, gocompare etc because I screwed the database. It gradually filled back up obviously. I won't do that again! Can I reword your post for you? "I was in charge of a big database that handled quotes for comparison websites. It broke a bit, and I decided to fix it but completely busted it." Use of master-master replication is fine for talking to clients and developers, but I think you need to know your general audience; in this case a load of football fans. I can forgive the real terminology of nodes, replication etc. but in our line of work (which will be similar to yours) the use of "RTO" is regarded as "BusinessSpeak 2.0-prat-talk" I thought Master-Master Replication meant that there would be two threads about the Portuguese league Link to comment Share on other sites More sharing options...
Recommended Posts