{"id":1124,"date":"2006-11-07T12:00:00","date_gmt":"2006-11-07T12:00:00","guid":{"rendered":"http:\/\/orcldoug.com\/blog\/?p=1124"},"modified":"2006-11-07T12:00:00","modified_gmt":"2006-11-07T12:00:00","slug":"recovery-design-part-5-wrap-up","status":"publish","type":"post","link":"http:\/\/orcldoug.com\/blog\/2006\/11\/07\/recovery-design-part-5-wrap-up\/","title":{"rendered":"Recovery Design Part 5 &#8211; Wrap-up"},"content":{"rendered":"<p>It&#8217;s been a very mini-series but I hope I&#8217;ve highlighted some of the challenges when designing systems that need to recover from failures quickly. Here are a few ideas and I&#8217;m sure others could add their own.<\/p>\n<ul>\n<li>Careful planning is essential.<\/li>\n<li>Ask tough questions and imagine the worst.<\/li>\n<li>Always be aware of the requirements. The design is entirely dependant on them.<\/li>\n<li>You need to consider every single point of failure and RAC still implies a single shared database that can fail (and probably will some day).<\/li>\n<li>Test.<\/li>\n<li>Keep things as simple as possible and minimise human intervention. Humans make mistakes.<\/li>\n<li>Test.<\/li>\n<li>Document. It reduces the number of mistakes humans might make.<\/li>\n<li>Test.<\/li>\n<li>Employ technically strong, responsible humans, and I swear that isn&#8217;t an advert, just recognition that the more complex the configuration, the better your people need to be.<\/li>\n<\/ul>\n<p>I mentioned in <a href=\"http:\/\/18.133.199.212\/?p=1120\">the previous part<\/a> that I would reach some unsatisfactory conclusions. Some of those are above &#8211; because I&#8217;m not telling you what to do, just mentioning some considerations &#8211; and here&#8217;s another. <\/p>\n<p>There really is no one-size-fits-all solution and (slay me for saying this, purists) the chances are that you will not deliver what the business wants, or what you hoped you would, but a compromise resulting from the balance of risks, costs and expectations. Far better to turn around and admit that if things go <i>very<\/i> wrong it might mean four hours down-time than come up with a pretty design document with the buzz-words that your managers are looking for and then have to spend four hours panicking when disaster strikes after the system&#8217;s live and five days explaining to managers why &#8216;it didn&#8217;t work&#8217;. <\/p>\n<p>As for the satisfactory sources of information, here are a few.<\/p>\n<p>I already mentioned Mogen&#8217;s first class <a href=\"http:\/\/www.miracleas.dk\/WritingsFromMogens\/YouProbablyDontNeedRACUSVersion.pdf\">critique of RAC<\/a> and I only recently came across another excellent RAC paper by James Morle that looks at <a href=\"http:\/\/www.scaleabilities.co.uk\/component\/option,com_remository\/Itemid,53\/func,fileinfo\/id,12\/\">RAC Connection Management<\/a>. Take a look at James&#8217; paper and ask yourself if you understand what &#8216;Transparent Application Failover&#8217; really means. It <i>sounds<\/i> perfect, but I guess it doesn&#8217;t do what most of you would expect (unless you&#8217;ve worked with it already).<\/p>\n<p>I&#8217;ve recently started reading the eBook version of Julian Dyke and Steve Shaw&#8217;s <a href=\"http:\/\/www.apress.com\/book\/bookDisplay.html?bID=458\">Pro Oracle Database 10g RAC on Linux<\/a>. Although I haven&#8217;t got into the guts of it yet, I&#8217;ve read all of the appendices and the first few chapters and the tone is pretty much what I&#8217;ve used in this series, but much more detailed. It&#8217;s very strong on high availability concepts so if you&#8217;ve never worked in that type of environment before, it&#8217;s a nice way to get started.<\/p>\n<p>Oh, one more thing. Vidya asked about disk-to-disk synchronisation and I thought I&#8217;d include a <a href=\"http:\/\/www.emc.com\/solutions\/continuity\/index.jsp?openfolder=bc\">link<\/a> for anyone who&#8217;s interested in that kind of thing, although it&#8217;s clearly vendor-specific<\/p>\n<p>The series is finished for now, but I think there&#8217;ll be future blogs about how the implementation of the new system goes, particularly any problems I run into.<\/p>\n<p>Looks like I&#8217;ll be back on PX for a couple of weeks &#128521;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It&#8217;s been a very mini-series but I hope I&#8217;ve highlighted some of the challenges when designing systems that need to recover from failures quickly. Here are a few ideas and I&#8217;m sure others could add their own. Careful planning is essential. Ask tough questions and imagine the worst. Always be aware of the requirements. The&hellip; <a class=\"more-link\" href=\"http:\/\/orcldoug.com\/blog\/2006\/11\/07\/recovery-design-part-5-wrap-up\/\">Continue reading <span class=\"screen-reader-text\">Recovery Design Part 5 &#8211; Wrap-up<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1124","post","type-post","status-publish","format-standard","hentry","category-uncategorized","entry"],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":1191,"url":"http:\/\/orcldoug.com\/blog\/2007\/01\/27\/dba-documentation-catalogue\/","url_meta":{"origin":1124,"position":0},"title":"DBA Documentation &#8211; Catalogue","date":"January 27, 2007","format":false,"excerpt":"Prompted by Linda's comment on a previous blog, I thought it might be worth writing a couple of postings on DBA documentation.The first thing you need is a Database Catalogue of some kind.Benefits1) Even an experienced DBA arriving on site won't know what servers exist, how to login to them,\u2026","rel":"","context":"With 11 comments","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1382,"url":"http:\/\/orcldoug.com\/blog\/2008\/02\/22\/how-useful-are-diagnosticoptimization-tools-another-view\/","url_meta":{"origin":1124,"position":1},"title":"&#8220;How useful are diagnostic\/optimization tools?&#8221; &#8211; Another View","date":"February 22, 2008","format":false,"excerpt":"There have been a couple of very interesting blog postings over the past few weeks from Daniel Fink and Alex Gorbachev, prompted by a panel discussion at last week's RMOUG conference. Well, I suspect the panel was prompted by an earlier blog posting and many late night conversations. I've just\u2026","rel":"","context":"With 25 comments","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/posts\/1124","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/comments?post=1124"}],"version-history":[{"count":0,"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/posts\/1124\/revisions"}],"wp:attachment":[{"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/media?parent=1124"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/categories?post=1124"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/orcldoug.com\/blog\/wp-json\/wp\/v2\/tags?post=1124"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}