2010 Disaster Recovery Guide

Transcription

1

2 SharePoit R 2010 Disaster Recovery Guide Joh L. Ferriger Sea P. McDoough Course Techology PTR A part of Cegage Learig Australia. Brazil. Japa. Korea. Mexico. Sigapore. Spai. Uited Kigdom. Uited States

3 SharePoit 2010 Disaster Recovery Guide Joh L. Ferriger Sea P. McDoough Publisher ad Geeral Maager, Course Techology PTR: Stacy L. Hiquet Associate Director of Marketig: Sarah Paella Maager of Editorial Services: Heather Talbot Marketig Maager: Mark Hughes Acquisitios Editor: Mitzi Kootz Project/Copy Editor: Kare A. Gill Techical Reviewer: J.D. Wade Iterior Layout Tech: MPS Limited, a Macmilla Compay Cover Desiger: Mike Taamachi Idexer: Larry Sweazy Proofreader: Sue Boshers 2011 Course Techology, a part of Cegage Learig. ALL RIGHTS RESERVED. No part of this work covered by the copyright herei may be reproduced, trasmitted, stored, or used i ay form or by ay meas graphic, electroic, or mechaical, icludig but ot limited to photocopyig, recordig, scaig, digitizig, tapig, Web distributio, iformatio etworks, or iformatio storage ad retrieval systems, except as permitted uder Sectio 107 or 108 of the 1976 Uited States Copyright Act, without the prior writte permissio of the publisher. For product iformatio ad techology assistace, cotact us at Cegage Learig Customer & Sales Support, For permissio to use material from this text or product, submit all requests olie at cegage.com/permissios. Further permissios questios ca be ed to permissiorequest@cegage.com. Active Directory, BitLocker, Forefrot, Groove, Hyper-V, IfoPath, ItelliSese, Iteret Explorer, MS-DOS, SharePoit, SQL Server, Visual Basic, Visual C#, Visual Studio, Widows Azure, Widows PowerShell, Widows Server, Widows Server System, ad Widows Vista are registered trademarks of Microsoft Corporatio. All rights reserved. VMware ad VMware Workstatio are registered trademarks of VMware, Ic. All other trademarks are the property of their respective owers. All images Cegage Learig uless otherwise oted. Library of Cogress Cotrol Number: ISBN-13: ISBN-10: eisbn-10: Course Techology, a part of Cegage Learig 20 Chael Ceter Street Bosto, MA USA Cegage Learig is a leadig provider of customized learig solutios with office locatios aroud the globe, icludig Sigapore, the Uited Kigdom, Australia, Mexico, Brazil, ad Japa. Locate your local office at: iteratioal. cegage.com/regio. Cegage Learig products are represeted i Caada by Nelso Educatio, Ltd. For your lifelog learig solutios, visit courseptr.com. Visit our corporate Web site at cegage.com. Prited i the Uited States of America

4 To Gretche ad Tracy, for their patiece, support, ad willigess to tolerate us doig this all over agai... ad so soo after the last book.

5 Ackowledgmets Sea P. McDoough would like to ackowledge the followig people ad groups: Microsoft, for cotiuig to evolve the SharePoit platform ad make it worthy of so may lost hours ad log ights. My may frieds ad family, for oce agai puttig up with my half-asleep moaig about coutless hours spet writig i the wee hours of the morig. Mitzi Kootz, for your patiece with a couple of kuckleheads like us. We re ot the fastest writers o the plaet, but we d like to thik that we re special i our ow way. Thaks for bearig with us ad admirably hadlig the situatio that laded i your lap. Julia Hall ad the folks at Idera, for givig us a forum ad helpig to icrease awareess for the cause of SharePoit disaster recovery. Your support of us ad our book has bee othig short of fatastic ad I m ot just sayig that because I happe to be workig for you these days. The SharePoit commuity-at-large. I ve greatly ejoyed my iteractios with so may of you at SharePoit Saturdays, at user group meetigs, at cofereces, o my blog, o Twitter, ad through all the other mechaisms that brig us together. You remai oe of the biggest reasos I keep sigig o for this puishmet. Kare Gill, for oce agai provig herself a fatastic copy editor ad teacher. Although I leared my lesso about edig seteces with prepositios from the last book, you foud plety of other ways to elighte me this time aroud. Thak you for patiece, diligece, ad istructio. J. D. Wade, aka The KB Ma, for doig a woderful job as our techical editor. It was t so log ago that I was sittig i your chair, J. D., so I have a special appreciatio for the role you filled with regard to this book. Thak you for all of your questios, suggestios, correctios, ad support. We simply could t have doe this without you. Joh Ferriger, a member of the SharePoit Mr. Clea Team ad my bald-headed parteri-crime. Thaks for aother go-roud with the DR Devil. We survived agai despite ourselves. Do you thik that oe of these days we ll lear? My mom, Ilee McDoough, who died uexpectedly just before this book wet to prit. I really wated to share this book with you. You would t have uderstood a thig it said, but that would t have chaged the excitemet ad smile o your face whe I haded you a copy. To my kids, Breda ad Sabria, who are still too youg to read this or uderstad what SharePoit is. Someday you ll be old eough to comprehed the cotets of this book, ad I hope that what you see brigs smiles to your faces. My wife Tracy. Before I eve started, you kew that it was goig to be aother rough ride with overrus, late-ight hours, ad a wor-dow husbad, yet you supported me with kidess, patiece, ad uderstadig the whole way. As with the first Disaster Recovery Guide, I could t have possibly doe this without you. Thak you. I love you so much. iv

6 Ackowledgmets v Joh L. Ferriger would like to ackowledge the followig people ad groups: My wife, Gretche, for the ubelievable support, patiece, ad ecouragemet she s give me through all of my hare-braied schemes, especially this oe. My parets, Berie ad Vicki, for the gift of readig ad the reassurace that they ll always be there to read to me. Erique Lima, for challegig me to always be better every day, puttig up with all my stupid questios, keepig me from goig off the deep ed, ad loaig me the hardware that made so much of my testig ad research possible. Mitzi Kootz for the limitless guidace ad tolerace she s had dealig with a couple of geeks who wat to sped every secod possible gettig it just right. Kare Gill, for oce agai makig it look like I write so purty, offerig ecouragemet, laughig at all my terrible jokes, ad eve tryig to fool me ito thikig that I m a good writer. J. D. Wade, for beig a precisio techical ace. I ve bee blessed to work with two icredible techical editors for both of our books, ad I kow that the value of what we ve put ito these pages is as much a result of J. D. s efforts as ours. Sea, for a millio more thigs tha I d ever be able to put ito words. For keepig me o task, for ever settlig, for puttig himself through this wriger agai, for writig icredible stuff, ad for beig a great fried. Piper, for makig every sleepless ight melt away with smiles, giggles, laughter, ad woder. For beig my favorite perso i the world to tickle ad a icredible blessig; I m so lucky to have you i my life. Gretche, you are first i this list because you are the most importat thig i my life, ad last i it because I always save the best for last. Everythig I do i this world is for you; you are my heart, my love, my best fried. Thak you for leadig me through this jourey agai. I will always love you.

7 About the Authors Sea P. McDoough is a product maager for SharePoit Products at Idera, a Microsoft goldcertified parter ad creator of tools for SharePoit, SQL Server, ad PowerShell. I his role as a product maager, he is focused o Idera s SharePoit backup ad recovery solutios. Sea carries several Microsoft Certified Techology Specialist (MCTS) certificatios for SharePoit ad other areas, ad he is a Microsoft Certified Professioal Developer (MCPD). He is also a regular speaker at SharePoit evets, a blogger, ad a developer of tools that simplify the admiistratio of SharePoit eviromets. Prior to joiig Idera, Sea served as a solutios architect ad SharePoit team lead at Cardial Solutios Group, a IT cosultig ad solutio provider, where he ot oly directed iteral growth of the SharePoit team, but helped foster ad grow Cardial s partership with Microsoft. As a cosultat, Sea worked with a umber of Fortue 500 compaies to architect, implemet, troubleshoot, tue, ad customize their SharePoit eviromets. Sea ca be reached through his blog ( LikedI ( likedi.com/i/smcdoough), or Twitter (@spmcdoough). Joh L. Ferriger, a solutios architect for Apparatus, Ic. i Idiaapolis, Idiaa, with more tha six years of experiece admiisterig ad supportig SharePoit techologies, has spet more tha 12 years workig i the iformatio techology cosultig idustry. He coauthored the SharePoit 2007 Disaster Recovery Guide, published by Charles River Media, i Jauary He is a MCTS i the istallatio ad cofiguratio of Widows SharePoit Services (WSS) v3, Microsoft Office SharePoit Server (MOSS) 2007, ad Microsoft System Ceter Operatios Maager (SCOM) He is also a Microsoft Certified IT Professioal (MCITP) for Eterprise Project Maagemet (EPM) with Project Server Joh speaks regularly at user groups, SharePoit Saturdays, ad other cofereces throughout the Midwest. He plas to make his triumphat retur to bloggig at com ow that this book is doe, besides writig articles ad postig at other great SharePoitrelated sites throughout the itercoected tubes of the Iteret. If you fid this book useful, Joh asks that you sed gifts of baco to Sea dow i Ciciati, because he eeds to see the error of his ways. Joh also admiisters a custom search egie idexig more tha 2,000 Web sites of SharePoit cotet. If you re lookig for iae commets, veted frustratios, or SharePoit wisdom i 140 characters or less, follow Joh o Twitter at vi

8 Cotets Itroductio xiv Chapter 1 SharePoit Disaster Recovery Plaig ad Key Cocepts 1 The Disaster Recovery Pla Cotext Key Cocepts ad Terms Assessmet ad Plaig Discovery ad Documetatio Depedecies ad Iterfaces Coclusio Chapter 2 SharePoit Disaster Recovery Desig ad Implemetatio 13 Defiig Scope What Are Recovery Targets? How Are Your Recovery Targets Defied? What Should Be Restored? What s Out of Scope What Are the Costs? Plaig the Recovery Process Documetig ad Implemetig the Disaster Recovery Desig Acquirig Resources Establishig a Disaster Recovery Baselie Documetig Your Procedures for a Outage Defiig the Commuicatio Pla...21 Determiig Success Coclusio vii

9 viii Cotets Chapter 3 SharePoit Disaster Recovery Testig ad Maiteace 25 Plaig Your Test Defiig the Scope of Your Outage Orgaizig Your Resources Verifyig Checklists ad Preparedess Coductig the Test Ecouragig Commuicatio Observig the Test Validatig the Pla Redesigig the Pla Performig Ogoig Maiteace of Your Disaster Recovery Pla Aalyzig Your Systems: As-Is/ To-Be Modifyig Your Pla Expectig ad Budgetig for Ogoig Maiteace...32 Coclusio Chapter 4 SharePoit Disaster Recovery Best Practices 35 Gettig to Kow Yourself Kow Your Scope Kow Your Budget Kow Your Ifrastructure...39 Gettig the Right Tool(s) for the Job What Does the Tool Cover? What Does t the Tool Cover? Ca the Tool Meet Your RTO ad RPO Targets? Usability Stability No Oe Size Fits All Coclusio Chapter 5 Widows Server 2008 Backup ad Restore 49 Backup Targets...50 Customizatios IIS...59 Widows Registry Providers ad Additioal Depedecies

10 Cotets ix Before You Begi Selectig a Backup Approach Backup Prerequisites Backig Up Widows Server Full Server Backup...78 Idividual Compoet Backup Restorig Widows Server Full Server Recovery Restorig Idividual Compoets Coclusio Chapter 6 Widows Server 2008 High Availability 117 Load Balacig Load-Balacig Software Load-Balacig Hardware Load Balacig ad SharePoit Farm Topology High Availability Storage Server Clusterig ad SharePoit Networkig ad Ifrastructure Plaig Coclusio Chapter 7 SQL Server 2008 Backup ad Restore 149 SharePoit s Database Optios How to Back Up a SQL Server 2008 Database Database Recovery Models Database Backup Types Backup Expiratio Settigs Backup Destiatios Overwrite Existig Backup Media Reliability Checks Database Sapshots Mirrored Backup Media Sets What s New i SQL Server 2008 Backup

11 x Cotets SharePoit ad Backig Up SQL Server What Ca Be Backed Up What Caot (or Should Not) Be Backed Up Database Sizig How to Restore a SQL Server 2008 Database Backup Restore Destiatio Optios Restore Source Optios Restore Optios Recovery State SharePoit ad Restorig a SQL Server 2008 Backup Overwritig SharePoit with a Restore of a SQL Backup Restorig a SQL Backup to a New SharePoit Eviromet Coclusio Chapter 8 SQL Server 2008 High Availability Log Shippig The Server Compoets of Log Shippig Log-Shippig Jobs How to Cofigure Log Shippig SharePoit ad Log Shippig Log-Shippig Pros Log-Shippig Cos Database Mirrorig The Server Compoets of Database Mirrorig How to Cofigure Database Mirrorig SharePoit ad Database Mirrorig Database Mirrorig Pros Database Mirrorig Cos Database Clusterig The Server Compoets of Widows Server Failover Clusterig Cofigurig Widows Server Failover Clusterig SharePoit ad Database Clusterig Database Clusterig Pros Database Clusterig Cos Coclusio

12 Cotets xi Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 241 Gettig Started A Overview of Backup ad Restore Capabilities Farm Backup ad Restore Graular Backup Cofiguratio-Oly Backup Backup/Restore Prerequisites ad Cosideratios Backup Settigs Services, Accouts, ad Permissios Full Backups Versus Differetial Backups Usig Uattached Cotet Databases Backig Up from Cetral Admiistratio Full Farm Catastrophic Backup Site Collectio Backup Exportig Cotet Uattached Cotet Database Data Recovery Restorig Withi Cetral Admiistratio Restorig a Full Farm Restorig a Cotet Database for Subsequet Uattached Recovery Operatios Restorig a Site Collectio or Exported Cotet Coclusio Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 299 Assumptios Settig the Stage Accessig the SharePoit 2010 Maagemet Shell PowerShell Backup ad Restore Prerequisites Scriptig SharePoit 2010 s Backup ad Restore Cmdlets Usig SharePoit 2010 s Catastrophic Backup Cmdlets Backup-SPFarm Backup-SPCofiguratioDatabase Backup-SPSite Usig SharePoit 2010 s Catastrophic Restore Cmdlets Restore-SPFarm Restore-SPSite

13 xii Cotets Reviewig Your Backup ad Restore History Documetig Your Cofiguratio Graular Backup ad Restore via PowerShell Export-SPWeb Import-SPWeb Coclusio Chapter 11 SharePoit 2010 Disaster Recovery Developmet 337 Hey Admiistrator I m Talki to You! The Dark Days Before PowerShell Admiistrative Capabilities with PowerShell The Disclaimer The Price of Admissio The SharePoit Object Model Extedig Catastrophic Backup ad Restore Through the SharePoit API Export, Import, ad Associated Types Site Collectio Backup ad Restore Programmatically Usig SQL Sapshots Volume Shadow Copy Service What Is VSS? Developig Solutios with VSS Rollig Your Ow Backup ad Restore Approach Object Model Walkig Employig Serializatio Surrogates Desigig Applicatios for Disaster Recovery Readiess Storage of Applicatio Cofiguratio Data Storage of Trasiet ad Persistet Applicatio Busiess Data Accessig Network Resources Applicatio Loggig ad Moitorig Coclusio Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 375 What Has Chaged i SharePoit A Word o Ed Users ad Disaster Recovery Tryig It Out

14 Cotets xiii Recycle Bis How They Work Recyclig i SharePoit Cofigurig Recycle Bis Versioig Types of Versioig Versioig Beefits Admiistrative Cocers Templates List Templates Site Templates SharePoit Desiger ad Templates A Admiistrative Perspective o Templates WebDAV ad Explorer View How WebDAV ad Explorer View Are Used Server ad Workstatio Cofiguratio Admiistrative Cocers SharePoit Workspace What Ca It Do? Admiistrative Cocers Coclusio Chapter 13 Coclusio 407 Idex

15 Itroductio If you ve doe ay previous research o SharePoit disaster recovery topics, such as cotet recovery, backup ad restore, ad high availability, you ve probably foud quite a bit of iformatio o the subject. That held true for us whe we wrote the origial Disaster Recovery Guide for SharePoit 2007, ad it s just as true ow with SharePoit But what we also foud was that much of the discussio did oe of two thigs: either it just scratched the surface of SharePoit disaster recovery, or it covered such a arrow focus that it was oly applicable i certai situatios. So we set out to create a resource for SharePoit disaster recovery that comprehesively examied the is ad outs of the various techical optios available to back up ad restore your SharePoit eviromet ad highlighted the cocers you eed to uderstad to build a iformed ad well-rouded disaster recovery pla. What You ll Fid i This Book Microsoft s SharePoit platform is a complex, diverse techical tool desiged to meet a rage of busiess eeds ad uses. It requires several other platforms ad applicatios for implemetatio, ad it ca be itegrated with other exteral lies of busiess applicatios. This diversity also applies to the umerous methods, tools, ad approaches that ca be used to preserve your Share- Poit farm if it becomes affected by a catastrophic evet. The majority of this book itroduces you to those methods, tools, ad approaches for backig up ad restorig SharePoit. Before coverig all the crucial techical aspects of preservig SharePoit with the tools Microsoft provides for it, we itroduce you to the key cocepts ad activities ecessary to develop a disaster recovery pla to implemet those techical practices. Listed ext are some of the mai cocepts this recovery guide discusses: Learig the cocepts ad termiology of SharePoit disaster recovery plaig Desigig ad documetig a SharePoit disaster recovery pla Testig ad maitaiig a SharePoit disaster recovery pla Uderstadig SharePoit-specific disaster recovery cocers ad best practices Backig up ad restorig the foudatio of ay SharePoit eviromet, Widows Server 2008 Uderstadig how high-availability techologies ca aid i SharePoit disaster recovery xiv

16 Itroductio xv Discussig the role that SQL Server ad its backup optios play i the SharePoit disaster recovery equatio Utilizig SharePoit s Cetral Admiistratio site for backup ad restore tasks Explorig the ew optios that are available through PowerShell ad SharePoit-specific cmdlets Ivestigatig the SharePoit object model ad how to employ custom developmet to meet special backup ad restore eeds Highlightig ed user disaster recovery optios ad the admiistrative cocers that are tied to them Who This Book Is For I geeral, this book is geared toward readers who are worried about the log-term health ad viability of their SharePoit eviromet ad the valuable busiess iformatio stored i it. It s assumed that readers are at least familiar with SharePoit as ed users, ad most of the techical cotet iside is best suited for those who have experiece deployig, cofigurig, ad admiistratig SharePoit. The examples, walk-throughs, ad advice i this recovery guide are iteded to be geeral ad ca be applied to a variety of situatios ad SharePoit eviromets. How This Book Is Orgaized Each chapter has relevat visual aids such as screeshots, diagrams, ad example documets to guide you through the topics beig discussed. You ll also fid special breakout sectios to call your attetio to items of ote, tips ad tricks, ad areas of cautio that we have foud particularly relevat. Fially, each chapter eds with a series of review questios iteded to test your uderstadig of what you ve completed ad help you thik about some of the chapter s key cocepts. Do t worry, though; we re providig aswers to those questios i Appedix A, Chapter Review Q&A. For more iformatio o Appedix A, see the Compaio Web Site Dowloads sectio that follows. Compaio Web Site Dowloads I additio to the cotets of this book, several additioal resources are available to you o the Cegage Learig Web site at Bous Chapter. This chapter discusses disaster recovery approaches for several commo SharePoit eviromets ad farm cofiguratios. These disaster recovery outlies itegrate a variety of the cocepts ad techologies discussed i this book, ad they may help you begi thikig about SharePoit disaster recovery plas i your ow eviromet(s).

17 xvi Itroductio Appedix A. This appedix cotais the aswers to the questios that are posed at the ed of each chapter i this book. If you wat to check your comprehesio of each chapter as you read it, be sure to go olie to grab the aswers i this appedix. Appedix B. This appedix is a alphabetical list of third-party backup ad restore tools that are available for SharePoit 2010 at the time this book was origially published. As much as we would have liked to cover each of these tools i the same depth we devoted to out-of-the-box optios from Microsoft, it just was t possible give timelies ad space costraits we were already up agaist. But that does t mea these tools are uworthy of metio, so i this appedix you ll fid a quick syopsis of each tool s attributes as provided by their maufacturer ad directio o where you ca fid out more.

18 1 SharePoit Disaster Recovery Plaig ad Key Cocepts I This Chapter The Disaster Recovery Pla Cotext Key Cocepts ad Terms Assessmet ad Plaig This book is writte primarily for iformatio techology (IT) professioals; as such, it devotes a sigificat umber of pages to strictly techical cocers. Topics such as high availability, SharePoit farm-level backup ad restore operatios, SQL Server log shippig, ad others are discussed at legth. Each of these topics is relevat to the cocept of SharePoit disaster recovery, but oe of them actually addresses the bigger picture of what costitutes a true disaster recovery strategy ad the cocers that drive the costructio of a ed-to-ed SharePoit disaster recovery pla. If you read SharePoit 2007 Disaster Recovery Guide, you may have oticed that this chapter ad the two followig it were positioed toward the back of the book i Chapters 12 through 14. We did that to ecourage readers to first uderstad the techical aspects of SharePoit disaster recovery, start to thik about how to select the right techical approach, ad the fit that approach ito a effective ad complete pla for the etire busiess, ot just SharePoit or the servers hostig it. Sice the SharePoit 2007 Disaster Recovery Guide was published, we ve spet sigificat additioal time workig o, researchig, ad talkig about SharePoit disaster recovery. Because of those efforts, we decided that you, the reader, would be best served by a overview of geeral disaster recovery cocepts before, rather tha after, a discussio of SharePoit disaster recovery techical specifics. Disaster recovery is ot just the practice of backig up your systems o a regular basis; it s a total commitmet to protectig your busiess s iformatio ad documets completely to meet the specific eeds of your users. I SharePoit 2010 Disaster Recovery Guide, we re startig off with three chapters o geeral disaster recovery ad the divig ito the techical mechaics of how to protect your SharePoit eviromet. We wat you to cosider each techical 1

19 2 SharePoit 2010 Disaster Recovery Guide solutio ad thik about how it might or might ot fit it ito your overall disaster recovery pla ad busiess cotiuity strategy. I this chapter, the focus is o geeral disaster recovery plaig: what drives a SharePoit disaster recovery strategy, the questios you must aswer before you ca formulate a techical solutio, ad other related strategic objectives ad cocers. This chapter also focuses o the cocepts, termiology, ad acroyms with which you must be fluet to speak the laguage of disaster recovery. The Disaster Recovery Pla Cotext It is certaily true that ay reasoable SharePoit disaster recovery strategy is goig to elist hardware ad software capabilities from a variety of applicatios ad platforms. To truly uderstad what drives the process of formulatig the disaster recovery pla that employs those capabilities, though, you eed to take a step back ad uderstad the cotext i which a disaster recovery pla is formed. Although SharePoit is a techical platform, umerous busiess users use the fuctios ad capabilities it provides i day-to-day operatios. Busiess users of a SharePoit farm deped o it for everythig from collaboratio ad sharig to publicatio ad busiess process automatio. Although those resposible for brigig a farm ad its fuctios olie followig a disaster might view disaster recovery as a techical exercise, the restoratio of fuctioality is critical to those who deped o SharePoit for daily operatios. It is i the ature of SharePoit admiistrators, solutios architects, ad those tasked with operatioal resposibilities to fid techical solutios to techical problems. O the surface, a disaster recovery pla looks like such a problem-solutio equatio. Disaster recovery plas ofte appear straightforward: a disaster happes, ad the disaster recovery pla goes ito effect. Operatios are shifted from the servers that wet dow to backup servers that are ruig i a alterate data ceter. The previously take backups are restored. That which is broke is fixed. Oce all steps are executed, everythig works as it did prior to the disaster. Right? Ufortuately, this view of disaster recovery ad disaster recovery plaig is somewhat aive. It s a commo mistake for SharePoit professioals ad iformatio techology professioals i geeral to thik of disaster recovery i strictly techical terms. Simply take eough backups, buy eough extra hardware, ad ret space i a additioal data ceter, ad all disaster recovery risks are mitigated. Project teams budget for disaster recovery without havig ay real idea of what s importat, what drives a appropriate disaster recovery strategy, ad what a busiessacceptable strategy really icludes or costs. I reality, the creatio of a disaster recovery pla is drive less by techical requiremets ad more by the potetial reveue losses associated with a system outage, damage to property ad materials by the absece of a operatioal system, the loss of commuicatios represeted by a dowed system, ad other similarly importat busiess factors. For these reasos, a properly

20 Chapter 1 SharePoit Disaster Recovery Plaig ad Key Cocepts 3 cosidered ad well-formed disaster recovery pla is a sigle piece of a larger busiess cotiuity pla that addresses ot oly the techical aspects of brigig a system back ito operatio, but all the other challeges that accompay it. These items iclude procedures for keepig iformatio secure, the chages i day-to-day operatios for persoel durig a declared disaster, cotiuity of commuicatios whe ormal chaels are dow, compliace measures associated with legal requiremets i the evet of a outage, ad so o. Key Cocepts ad Terms The domai of busiess cotiuity plaig possesses a somewhat uique set of cocepts, terms, ad processes. To cotiue buildig o the cocepts ad drivers associated with disaster recovery plaig, Figure 1.1 zooms out to look at the larger, more holistic process of busiess cotiuity plaig ad where SharePoit disaster recovery plaig fits ito it. Figure 1.1 The stages of busiess cotiuity plaig. As illustrated i Figure 1.1, busiess cotiuity plaig ivolves three distict stages: 1. The risk assessmet. The risk assessmet is where disaster recovery plaig begis. It etails the aalysis of a SharePoit farm ad the busiess processes tied to it from the perspective of vulerabilities, threats, ad geeral exposures that are itroduced simply by havig the farm i productio ad i use by busiess users. The idetifiable risks typically equate to oe or more SharePoit fuctios or usage scearios. Collaboratio o XYZ project, busiess itelligece fuctios leveraged by executives, ad workflow that is used to approve public commuicatios i the ABC documet library are examples of such fuctios ad scearios. 2. The busiess impact aalysis (BIA). The results of the risk assessmet serve as the iput to the BIA. The BIA attempts to equate the loss of a particular SharePoit capability or fuctio (such as the loss of busiess itelligece fuctios leveraged by executives) with the projected magitude or expected moetary impact associated with the loss (for example, $10,000 per day i ivestmets). Equatig outages to exact losses is difficult at this stage due to all the variables that are typically i play, but the results of the aalysis serve as a valuable prioritizatio tool i the ext stage of the busiess cotiuity plaig process. 3. The busiess cotiuity pla (BCP). Armed with the results of the BIA, busiess cotiuity plaers possess the data they eed to prioritize ad address the risk areas idetified durig the risk assessmet. Risk areas or regios that the BIA idetifies as

21 4 SharePoit 2010 Disaster Recovery Guide carryig the largest potetial for loss or adverse busiess exposure are addressed more urgetly, whereas those with lesser potetial impact are addressed whe the opportuity arises or is most cost effective. As described earlier, the BCP that results from this process addresses both the techological areas icluded i the disaster recovery pla (such as restore the system ad associated databases from backup ) ad associated busiess processes (for example, have the accouts payable team begi usig the ew repository at URL istead of the stadard productio URL ). A BCP typically icludes other prescriptive advice ad workarouds to miimize or mitigate the impact of a outage. As show i Figure 1.1, a disaster recovery pla is oe compoet of the ultimate busiess cotiuity pla that results from both the risk assessmet ad BIA of idetified risks. Of course, the disaster recovery pla does ot simply arise from a determiatio regardig the potetial impact of a outage. The purposes for which a SharePoit farm is used, alog with acceptable outage widows i the evet of a disaster, ultimately drive the techological aspects of the disaster recovery pla that a orgaizatio crafts ad implemets. Two key cocepts determie what costitutes a acceptable outage widow: Recovery time objective (RTO). The RTO of a disaster recovery pla defies the amout of time that ca elapse betwee the occurrece of a disaster ad the affected system beig retured to a agreed-upo level of operatioal readiess. Put simply, a RTO defies the time you have to get a system back up ad ruig after a disaster. It is typically durig this period that the steps of a disaster recovery pla are executed. A highly critical SharePoit system may have a real-time RTO (that is, the failure of a productio system immediately results i a backup system takig over). At the other extreme, a farm that hadles tertiary busiess fuctios may have a RTO that is measured i weeks to support the acquisitio of ew hardware ad the ultimate rebuild of the farm from scratch. Recovery poit objective (RPO). Whereas RTOs are forward-lookig, a RPO defies a period of time prior to ay disaster where data loss may (ad likely will) occur. Crudely explaied aother way, a RPO defies the maximum amout of data loss that s deemed acceptable i a disaster. Data that existed prior to the poit i time defied by the RPO ca be restored or recovered, whereas data after that poit may ot. As you might expect, a highly critical SharePoit system may have a disaster recovery pla with a ear-zero RPO that does ot accept ay form of data loss. Tertiary systems, o the other had, may have RPOs that are measured i hours or days. To illustrate the cocepts of RTO ad RPO, cosider the disaster recovery pla profile show i Figure 1.2. The requiremets i this pla are commo of less-critical systems, where some amout of data loss ad dowtime is deemed acceptable i the evet of a disaster.

22 Chapter 1 SharePoit Disaster Recovery Plaig ad Key Cocepts 5 Figure 1.2 RPO ad RTO for a SharePoit farm of lesser busiess sigificace. I this disaster recovery pla, a disaster occurs ad is declared at 7 a.m. The disaster recovery pla madates a RPO of 12 hours ad a RTO of 24 hours. To satisfy the RPO requiremet of this pla, a backup or some capture of relevat data ad state must have bee performed i the 12 hours leadig up to the declaratio of the disaster. At the same time, the RTO requiremet states that the system must be restored to a fuctioal state (qualified withi the disaster recovery pla) withi 24 hours of the disaster s occurrece. Figure 1.3 presets a differet set of requiremets for recovery whe the disaster is declared at 7 a.m. The RTO ad RPO show are more commo of a SharePoit farm that is of greater importace to the orgaizatio that utilizes it. With a RPO widow of oe hour ad a RTO widow of 30 miutes, the potetial overall outage widow is sigificatly smaller tha the oe illustrated i Figure 1.2. Figure 1.3 RPO ad RTO for a SharePoit farm of greater busiess importace. As you might imagie, implemetig a disaster recovery solutio to address the RTO ad RPO requiremets illustrated by the pla show i Figure 1.3 carries a differet set of challeges tha meetig the requiremets for the pla show i Figure 1.2. Techical strategies ad supplemetal equipmet requiremets vary sigificatly betwee the two.

23 6 SharePoit 2010 Disaster Recovery Guide Note: A discussio of the specific meas by which you ca address the techical ad material requiremets of a SharePoit disaster recovery pla takes place ext i Chapter 2, SharePoit Disaster Recovery Desig ad Implemetatio. I a perfect world, all disaster recovery strategies would ivolve o loss of data (that is, have a zero RPO widow) ad provide istat failover (zero RTO). Ufortuately, the cost of such strategies for SharePoit farms is exceptioal ad prohibitive for all but the most critical of busiess uses. As part of their disaster recovery plaig, most orgaizatios discover that as RPO ad RTO target widows shrik, the cost of a associated disaster recovery strategy goes up. The challege the becomes balacig data loss ad dowtime agaist the total cost of implemetig a appropriate ad effective disaster recovery strategy. Assessmet ad Plaig The precedig sectio highlighted the geeral processes that evetually lead to the formatio of a SharePoit disaster recovery pla. It was show that i the early stages of the busiess cotiuity plaig process, the bulk of the plaig ad decisio makig is drive by busiess owers ad those who are capable of assessig the dollar value of the capabilities ad fuctios that a Share- Poit farm provides. Techical owers typically have a part to play i this process, but they do t drive it. This is ot to say that disaster recovery plaig should be left etirely to busiess owers util the process evetually flows dowstream to those with techical resposibilities. O the cotrary, SharePoit techical owers ca udertake umerous assessmet ad plaig activities i advace of their ivolvemet i the busiess cotiuity plaig process. By stayig ivolved i the plaig process, SharePoit admiistrators ca esure that the fiished product is viable from both a busiess ad a techical perspective. Otherwise, busiess owers may base their decisios o icomplete or iaccurate estimates ad place umaageable burdes upo the architecture or costs of your SharePoit eviromet. Fially, it is worth otig that the terms busiess ower ad techical ower are used primarily to idetify roles for plaig ad usage, ot specific idetities or groups withi a orgaizatio. Iformatio techology groups commoly fid themselves i the role of SharePoit techical ower, but it is relatively commo for IT to also assume the role of busiess ower whe their ow processes, data, ad itellectual property are stored withi a SharePoit eviromet. I such circumstaces, it is reasoable to expect that IT employees would ow SharePoit disaster recovery plaig from ed to ed ad drive it themselves. A mysterious busiess ower would t suddely become ivolved to esure that IT remais solely i the role of techical ower. Discovery ad Documetatio I the early stages of disaster recovery plaig, the goal for SharePoit techical owers is to fully uderstad ad documet the farm or farms they re resposible for. If the SharePoit farm

24 Chapter 1 SharePoit Disaster Recovery Plaig ad Key Cocepts 7 is t yet i productio or is still i the plaig stages, the expected operatioal ed state should be the target of activities. This sort of aalysis ad documetatio is a worthwhile objective eve without the cotext of disaster recovery plaig, but the kowledge ad artifacts delivered by the process are a critical iput ito the desig ad implemetatio phases that are discussed i the ext chapter. Tip: The Uified Modelig Laguage (UML) is a excellet tool for commuicatig the iformatio gathered durig this phase of the disaster recovery plaig process. Created by the Object Maagemet Group (OMG), the UML provides a set of guidelies ad stadards for the documetatio of applicatio architecture ad structure. More iformatio is available at the OMG s UML resource page at Focus discovery ad documetatio o four key areas: logical architecture, physical deploymet, cofiguratio data, ad busiess data. Logical Architecture The logical architecture model of a system describes the logical compoets of the system, the purpose each of the compoets serves, ad how the compoets iteract with oe aother. It is also commo for a system s logical architecture model to idetify iterfaces ad other poits of cotact betwee the system ad other resources ot tied directly to the system. Whether based strictly o SharePoit Foudatio 2010 or SharePoit Server 2010, all Share- Poit farms possess a umber of architectural aspects that should be documeted before disaster recovery plaig. Amog these are the followig: Iteret Iformatio Services (IIS) applicatio pools SharePoit Web applicatios Service Applicatios, such as Search or Busiess Coectivity Services (BCS) Zoes ad associated alterate access mappigs Web applicatio policies Cotet databases Site collectios (icludig host-amed site collectios) Sites My Sites SharePoit farms that are based o SharePoit Server (ot SharePoit Foudatio) have additioal architectural aspects that must be cosidered i additio to those just metioed. The

25 8 SharePoit 2010 Disaster Recovery Guide specifics vary based o the editio of SharePoit Server i use, but may of the ehacemets revolve aroud additioal services ad applicatios such as PerformacePoit Services, FAST search itegratio, ad IfoPath Forms Services. Whe documetig the logical architecture of your SharePoit farm, direct your focus primarily to the logical compoets that are preset ad how they iteract with oe aother rather tha the capture of all details associated with settigs ad cofiguratio. Some amout of cofiguratio data is typically icluded withi the documeted model to accurately describe aspects of the logical architecture, but all of the itty-gritty cofiguratio ad settig data is best ivetoried separately as part of SharePoit disaster recovery plaig. Physical Deploymet The physical deploymet model of a system describes the system s implemetatio across a specific set of ifrastructure compoets ad hardware. Whereas the logical architecture model of a system focuses primarily o the compoets of a system ad how they iteract, the physical deploymet model of a system gets ito the specifics of the eviromet i which the system resides ad operates. Most physical deploymet models have a umber of similar characteristics regardless of the system or applicatio beig documeted, ad SharePoit physical deploymet models are o exceptio. Such models commoly iclude both the hardware that directly costitutes the Share- Poit farm ad ay acillary hardware that is exteral to the immediate farm but required for the proper overall fuctioig of the SharePoit eviromet. Commoly foud elemets iclude these: Physical servers that both SharePoit ad SQL Server use Storage equipmet such as storage area etworks (SANs) ad etwork-attached storage (NAS) devices Switches ad other core etworkig equipmet Wide area etwork (WAN) coectios ad other remote access liks Firewalls that are betwee or touched by SharePoit servers Hardware load balacers, stad-aloe IP address maagemet (IPAM) devices, ad other specialty equipmet Other supportig hardware, such as Widows Active Directory (AD) domai cotrollers As with the logical architecture model, you should place greater emphasis o idetifyig the physical compoets of the SharePoit farm tha o capturig every cofiguratio settig associated with the ifrastructure ad hardware. Some cofiguratio ad settig data is aturally

26 Chapter 1 SharePoit Disaster Recovery Plaig ad Key Cocepts 9 icluded as part of the physical deploymet documetatio, but a exhaustive treatmet of cofiguratio ad settig data takes place i the ext sectio, Cofiguratio Data. Cofiguratio Data Cofiguratio data is ay data that is required for proper operatio of a system, both iterally ad withi its implemetatio eviromet. Applicatios ad systems use ad store cofiguratio i a variety of ways, such as via files, databases, ad the Widows Registry. Typical Share- Poit farms leverage umerous cofiguratio settigs ad settigs storage facilities. Just three examples of the may locatios ad facilities withi SharePoit aloe iclude these: Cofiguratio, Search, ad Service Applicatio databases Web.cofig files for SharePoit Web applicatios IIS7 cofiguratio files (formerly the IIS metabase) You ca target each of the examples listed with relative ease for automated backup operatios. These items represet oe type of cofiguratio data you should capture whe focusig o SharePoit disaster recovery plaig. Documetatio should iclude a descriptio of each item, the locatio of the item (such as a database ame or full file system path), ad how the iformatio represeted by the item is used. The secod type of cofiguratio data you must capture is data that is critical to farm operatios but does ot led itself to easy targetig for backup. This ca be data that is stored i multiple locatios but must remai sychroized across all locatios, data that is difficult to access due to its storage locatio or form, or eve data that depeds o or is stored withi exteral systems. Two commo examples of data that falls ito this overall category are service accouts ad passwords that are hashed prior to their storage. Cofiguratio data that falls ito this secod category does ot led itself to the same style of capture that was described for data that is easily backed up. Documetatio should iclude the relevat iformatio (such as service accout userame ad password), the purpose of the iformatio, ad some idicatio of how the iformatio is supplied or etered ito the SharePoit eviromet. (The latter might be a referece to the Maage Accout page withi the Cetral Admiistratio site where a admiistrator supplies the accout iformatio required to have SharePoit maage the accout.) Note: For reasos of security, may orgaizatios elect to track each of the two types of cofiguratio data separately. Because data fallig ito the secod category typically cotais sesitive or restricted iformatio, a orgaizatio s computer iformatio security group or persoel operatig i a similar role ofte maage it. At a miimum, cotrol or limit access to this type of data to a defied group of persoel to avoid its misuse.

27 10 SharePoit 2010 Disaster Recovery Guide Busiess Data Whereas cofiguratio data is iformatio that a system uses to permit it to operate as desiged, busiess data is iformatio that flows through the system, is processed by the system, ad is ofte stored by the system durig the course of day-to-day operatios. Busiess data is the data that ed users care about ad that ormally has a dollar value attached to it durig BIA activities. Busiess data ca also be restricted by a orgaizatio s iteral policies or govered by laws such as the Sarbaes-Oxley Act of 2002 ad Health Isurace Portability ad Accoutability Act (HIPAA). Fortuately for disaster recovery plaers, SharePoit uses a cosistet ad cetralized storage model for the bulk of the busiess data it hadles. Data goig ito SharePoit typically eds up i a SQL Server database. I the case of documets ad attachmets, data is commoly stored i a cotet database uless the cotet database has bee cofigured to use a Remote Blob Storage (RBS) provider. I the absece of a RBS provider, the act of documetig cotet databases, their site collectios, ad the data that is cotaied withi them arms you with the iformatio you eed to guide the developmet of a recovery strategy for documets ad attachmets. If you implemet a RBS provider, you ll eed additioal documetatio steps to address the locatio or system this is directed toward. I additio to cotet databases, SharePoit 2010 uses may Service Applicatios for everythig from maaged metadata to user profile iformatio. These Service Applicatios commoly utilize SQL databases of their ow for busiess data storage. Documetig the Service Applicatios that a SharePoit farm exposes ad cosumes, as well as the databases supportig these Service Applicatios, is a importat step to esure that busiess data does t fall through the cracks. Fially, it is worth otig that a SharePoit farm that leverages BCS withi SharePoit 2010 may expose ad surface busiess data through SharePoit that actually resides somewhere other tha the SharePoit farm. The seamlessess with which exteral lists ad exteral cotet types expose data for use ca make it difficult to differetiate betwee SharePoit-residet data ad busiess data residig withi exteral lies of busiess systems. Whe documetig busiess data, it is imperative that you research ad clearly idetify the system of origi. Depedecies ad Iterfaces Judiciously documetig the four areas just discussed provides a overview of the SharePoit farm ad how it operates, the eviromet it operates i, ad how SharePoit-based data is cosumed ad processed. For SharePoit farms that operate idepedetly of all other systems, this is all the iformatio you eed to prepare for the more formal process of disaster recovery desig. Ufortuately, few orgaizatios use oly SharePoit. Most orgaizatios usig SharePoit also have some combiatio of systems, file shares, additioal lie of busiess solutios, homegrow applicatios, ad a whole host of additioal systems too volumious to eumerate. Realizig the value of SharePoit whe used as a portal or itraet solutio, may orgaizatios go to great legths to itegrate SharePoit with these systems.

28 Chapter 1 SharePoit Disaster Recovery Plaig ad Key Cocepts 11 For purposes of disaster recovery plaig, these exteral itegratio poits represet areas that require special attetio. A SharePoit farm that is restored to a fully operatioal state without exteral systems ad stores it depeds o is ot goig to be viewed as fully operatioal i the eyes of busiess users. Whe documetig the logical architecture, physical architecture, cofiguratio data, ad busiess data associated with a SharePoit farm, pay particular attetio to iterface poits with other systems, stores, ad services that are leveraged or represeted i some form withi SharePoit without actually beig part of the farm themselves. Examples of such depedecies ca iclude the followig: Lie of busiess systems that publish data cosumed through SharePoit s BCS fuctioality Custom user cotrols ad Web Parts that iterface with Web services exposed by other systems Service Applicatios i other farms that the target SharePoit farm cosumes IfoPath forms that iclude logic to write portios of submitted form data to a o-share- Poit SQL Server database A simple Page Viewer Web Part that provides a browser-based view of a file share Busiess users would likely judge a full restoratio of the associated SharePoit farm without associated exteral systems as SharePoit beig less tha fully fuctioal. Idetifyig depedecies ad iterfaces with other systems goes beyod simply documetig a SharePoit farm. It requires a aalysis of the purposes of a farm s site collectios, a ivetory of implemeted features (such as IfoPath forms ad BCS coectios to lie of busiess systems), ad a uderstadig of the operatios beig carried out by custom SharePoit solutios ad compoets ruig withi the farm. Ofte this process ultimately cosumes more time tha the documetatio of the SharePoit farm. Nevertheless, the kowledge gaied by the idetificatio of these depedecies ad iterfaces is critical to ay complete SharePoit disaster recovery pla desig. Coclusio Iformatio techology persoel ofte regard SharePoit disaster recovery plaig as a techical problem that is theirs to solve, but i reality, a disaster recovery pla is just oe part of the larger busiess cotiuity plaig process. If the disaster recovery pla for your SharePoit eviromet is goig to be a effective piece of your orgaizatio s overall BCP, you must be ready to ivest sigificat time creatig a risk assessmet ad a BIA. Otherwise, the etire BCP is at risk ad fails to provide a ecessary ad critical service to your busiess. Two critical iputs to the disaster recovery plaig process come i the form of RTOs ad RPOs. These two parameters defie the widow of available recovery time (RTO) ad the widow of acceptable data loss (RPO) for a SharePoit farm (or some part of it) whe a disaster has