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 [email protected]. 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

29 12 SharePoit 2010 Disaster Recovery Guide bee declared. Disaster recovery plaers commoly face the challege of tryig to balace dowtime ad data loss agaist implemetatio costs. As RTO ad RPO widows shrik, costs associated with appropriate disaster recovery strategies typically rise disproportioately. A SharePoit disaster recovery desig depeds o the completio of several busiess processes to proceed i a iformed fashio, but techical owers ad those resposible for SharePoit farms ca prepare for the desig process i a couple of ways. Of greatest importace is the documetatio of the SharePoit farm. Detailig the logical architecture, physical deploymet, cofiguratio data, ad busiess data aspects of a SharePoit farm provides disaster recovery plaers with recovery targets ad usage iformatio that are ivaluable durig the desig stage. Also of critical importace i the assessmet process is the idetificatio of SharePoit iterfaces to other systems ad exteral farm depedecies. Although these o-sharepoit systems may ot techically be a part of the SharePoit farm, itegratio with these systems meas that you must address them i some fashio durig disaster recovery desig. Havig completed this chapter, you should ow be able to aswer the followig questios. As with the other chapters, aswers to the followig questios appear i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at dowloads. 1. How do a disaster recovery pla ad a busiess cotiuity pla differ? 2. What is the differece betwee a RPO ad a RTO? 3. How does cofiguratio data differ from busiess data? 4. Why are iterface poits with other systems so importat to capture durig iitial aalysis? 5. Name some commo iterface poits betwee SharePoit ad other systems that require special aalysis ad treatmet durig disaster recovery documetatio.

30 2 SharePoit Disaster Recovery Desig ad Implemetatio I This Chapter Defiig Scope Plaig the Recovery Process Documetig ad Implemetig the Disaster Recovery Desig May admiistrators of iformatio techology (IT) systems are all too familiar with that famous axiom kow as Murphy s Law, which says, If aythig ca go wrog, it will. Although it may soud fatalistic, havig the expectatio that oe day dow the road a mishap of oe kid or aother will happe to your SharePoit eviromet is a importat perspective to maitai whe desigig ad creatig your orgaizatio s disaster recovery pla. This is t somethig you should geerate for the sake of crossig a item off your To-Do list or checkig a check box i a survey or audit. A effective disaster recovery pla gives you a resource you ca use i all situatios, regardless of scope or importace. By ot losig sight of the fact that this strategy is goig to be used ad ot just gather dust somewhere, you are drastically improvig your chaces for a successful recovery of your busiess s crucial SharePoit systems ad data whe the chips are dow. Now that you ve bee itroduced to the cocepts ad termiology of disaster recovery i Chapter 1, SharePoit Disaster Recovery Plaig ad Key Cocepts, it s time to start applyig those lessos to your orgaizatio s requiremets ad costraits. This chapter is desiged to walk you through the process ecessary to desig ad documet your disaster recovery pla. You will gai a uderstadig of the data you eed to collect ad maitai i your pla, the parameters ecessary for ot oly its desig but its success, ad ways to record all that data i a cosistet, coheret fashio. Defiig Scope It s impossible to pla how you will recover your system i the evet of a outage or disaster without uderstadig what your system is composed of ad what its critical compoets are. For may complex eviromets, it simply is t feasible to attempt to fully restore every server, applicatio, or database at the same time; tryig to do so would add hours, days, or eve weeks 13

31 14 SharePoit 2010 Disaster Recovery Guide to the time it would take to complete this vital restoratio activity. That is why the first step you must take whe developig your disaster recovery pla is to defie its scope ad to evaluate ad select the essetial parts of your system that must be restored i the evet of a disaster. Note: It s assumed that you re ot desigig ad developig your SharePoit eviromet s disaster pla o your ow, or oly from a IT perspective. As discussed i Chapter 1, a disaster recovery strategy is simply part of a larger busiess cotiuity pla (BCP) that s drive primarily by busiess stakeholders ad the cost that is tied to outages i a SharePoit eviromet. Although you, as a admiistrator, kow what ifrastructure compoets you eed to have i place to restore your eviromet, your users are the oes who should determie which sites are busiess critical, what cotet should be preserved at all costs, ad what the acceptable levels of dowtime are for these items. The results of a busiess impact aalysis (BIA) serve as the primary guide whe costructig your disaster recovery pla. What Are Recovery Targets? Recovery targets are the critical fuctios ad data of your SharePoit eviromet that eed to be restored followig the declaratio of a disaster. Seems pretty straightforward, does t it? Well, thaks i part to the complex ad modular ature of a SharePoit eviromet, that is ot always the case. Recovery targets are importat because ot oly do they idetify the parts of your system that eed to be ackowledged ad addressed i some way as a part of your disaster recovery pla, but they are the fuctios ad data that must be restored or replaced as part of a successful recovery operatio. A set of recovery targets reads like a checklist, ad recovery targets are ofte used i this fashio durig disaster recovery testig to gauge the success or failure of a recovery strategy followig its executio. How Are Your Recovery Targets Defied? Recovery targets are defied through the process of mappig the results of a BIA (that is, the data ad fuctioality that busiess stakeholders have idetified as beig critical i a SharePoit farm) to elemets withi the farm that were idetified durig the discovery ad documetatio phase described i Chapter 1. Each result from the BIA should traslate to oe or more techical fuctios ad data elemets withi the SharePoit farm. For example, cosider a BIA that idetifies a SharePoit site housig olie actuarial capabilities as beig highly critical to daily busiess operatios. Techical aalysis ad cross-referecig of the site metioed i the BIA might yield umerous recovery targets, icludig these: The cotet database housig the SharePoit site cotaiig Excel spreadsheets The Excel Services Service Applicatio providig olie calculatio fuctioality

32 Chapter 2 SharePoit Disaster Recovery Desig ad Implemetatio 15 The physical server that is dedicated withi the farm to carry out the processor-itesive Excel calculatios The uatteded service accout userame ad password that Excel Services uses for several trusted data coectios A custom trusted data provider that is defied withi the Excel Services Service Applicatio Several legacy lie of busiess systems that are accessed through trusted data coectios to supply data for the actuarial spreadsheets As you ca see, a seemigly straightforward busiess fuctio could lead to a cascadig list of techical requiremets durig the defiitio of recovery targets. For large SharePoit farms, the recovery targets that are ultimately selected may comprise oly a subset of the farm s total fuctioality. This is especially true if the recovery time objective (RTO) for the fuctios ad data specified is extremely aggressive ad the disaster recovery pla ivolves a substatial maual effort to carry out. What Should Be Restored? As the results of the BIA are mapped to recovery targets, you may begi to see that some techical fuctios or data withi your farm have a higher priority tha others ad that some pieces of key techical fuctioality or data are required to make their associated busiess fuctios available i SharePoit. It s also perfectly ormal for some techical fuctios to be idetified as low-priority compoets that ca be restored oce your farm s core cotet ad techical fuctioality have bee fully restored ad verified. This kid of triage activity ca be beeficial, because it helps you to focus your activities ad eergy o the most importat aspects of your eviromet without gettig distracted by targets of lower priority. Ofte this exercise ca help you uderstad that it is t a good idea to fully restore your productio eviromet immediately after a outage. Aother beefit of this aalysis is the impact it ca have o the architecture, cofiguratio, ad goverace policies of your SharePoit farm to better positio or partitio key elemets for recoverability based o busiess value ad associated disaster recovery priority. Followig are a few other factors that you should keep i mid as you aalyze the BIA results ad cosider the recovery targets that result: Cotet database distributio. How are sites ad site collectios i your farm distributed across cotet databases? Cosider storig high-priority sites i specific or uique cotet databases to allow more frequet backups to be made o those databases ad prevet lesser sites from usig resources. Carefully distributig your sites across databases, ad eve database istaces, ca make your backup ad restore processes much easier to maage ad complete. Cotet. What types of cotet or data do users store i differet types of sites i your farm? Is the cotet that users store i their My Sites give the same recovery priority by the BIA as

33 16 SharePoit 2010 Disaster Recovery Guide what they store i collaborative team sites? Your orgaizatio may already have usage ad retetio policies that ca help to aswer these questios about the cotets of differet types of sites ad determie whe they should be backed up ad restored i the absece of specific directives by the BIA. Service Applicatios. SharePoit Foudatio uses a umber of Service Applicatios, ad SharePoit Server 2010 icludes a eve greater umber. If your recovery strategy ivolves some form of maual rebuild or recofiguratio, it is importat to uderstad the usage patters for the Service Applicatios i your SharePoit farm. I the actuarial example that was metioed earlier, Excel Services are critical to the restoratio of busiess fuctioality ad would likely receive a high priority for recovery. Excel Services could be ru locally withi the farm, or the service could be cosumed from aother farm etirely. Recogizig both the importace of the Service Applicatio ad the actual origi of services provided is key i the proper defiitio of recovery targets. Depedet systems ad iterfaces. What applicatios or cofiguratio items have bee idetified as recovery targets o your productio servers to support the various fuctios of your SharePoit farm? Some applicatios provide crucial data or fuctioality to the users of your SharePoit farm ad must be recoected or restored as part of your farm s restore effort. Other applicatios are ot idetified by the BIA as missio critical ad are therefore ot a priority. What s Out of Scope It s just as importat to establish what s out of scope for your disaster recovery pla as it is to idetify what s i scope. This is t a simple exercise of listig what platforms, applicatios, systems, or compoets are ot icluded i your disaster recovery pla. Yes, such actios are defiitely part of the scope defiitio process, but it s also importat to determie what other groups are beig expected to support ad idetify those items deemed to be out of scope for your pla. For example, if database admiistrators (DBAs) exteral to your group maage your SharePoit databases, it may be possible to declare the disaster recovery of those databases out of scope to your pla because those DBAs will hadle them. Tip: Establishig exteral depedecies withi a disaster recovery pla itroduces risk ad is ot the right of SharePoit techical owers. Prior to portios of a pla becomig depedet o exteral systems or persoel, discussios with busiess owers ad stakeholders must take place. Although SharePoit techical owers ad persoel are ultimately resposible for meetig the recovery objectives idetified through the BIA, busiess stakeholders are the oes assumig the risk ad realizig the ultimate impact of a system outage.

34 Chapter 2 SharePoit Disaster Recovery Desig ad Implemetatio 17 What Are the Costs? As professors of ecoomics are ofte fod of statig, There s o such thig as a free luch. Every choice ad decisio you make aroud your disaster recovery pla has a direct impact o how much it will cost to implemet that pla. Frequet backups ca require extesive storage resources, as well as more time to cofigure, test, ad maitai. Optig to restore every aspect of a farm as quickly as possible is certaily possible, but the hardware, software, ad workforce resources ecessary to pull off such a pla ca prove prohibitively high for all but the largest of eterprises. It s essetial to uderstad the costs iheret i each aspect of a disaster recovery pla so that you ca balace ad cosider them as part of the pla. You may fid that the best solutio is ot always the right solutio for your orgaizatio oce you itroduce costs ad expeses ito the equatio. Plaig the Recovery Process After you ve established the recovery targets based o the BIA, it s time to move o to the steps you must take to actually retur your system to acceptable levels of fuctioality. It s time to start determiig the people, hardware, software, ad other resources that eed to be i place before you ca start the recovery process. Durig the plaig ad desig process, it s commo to discover that the level of recoverability that busiess owers desire is t possible with the budget allotted to disaster recovery operatios. At this stage, bargaiig ad compromise are commo to reach levels of recoverability ad cost that are acceptable to both busiess stakeholders ad SharePoit farm owers. Settig aside issues of cost, there are a umber of additioal areas to cosider as you begi the process of recovery plaig ad desig. May factors ad drivers are commoly ucovered as a pla evolves, ad your approach should be flexible eough to respod to them, but at a miimum a effective disaster recovery pla is built with strog cosideratio for the followig three aspects: RTO ad RPO. After readig Chapter 1, you should be familiar with the cocepts of RTO ad RPO (recovery poit objective) ad how they impact techical optios regardig recoverability. The requiremets that are established for each recovery target s RTO ad RPO directly affect your pla s desig, which must be able to meet those objectives to be effective. RTO ad RPO ca dictate the type ad umber of resources you eed to have available to execute the pla, the sorts of tools ad rage of feasible techologies you use to preserve ad restore your system, ad the way you defie your success criteria. Your data. What cotet, such as busiess documets or task lists, must be immediately restored to eable your users to remai productive? How is that data stored withi your SharePoit eviromet, ad how easily ca it be backed up ad restored? These cosideratios impact your pla, the tools you use to implemet it, ad the ifrastructure you put i place to support it.

35 18 SharePoit 2010 Disaster Recovery Guide Physical limitatios. The tagible pieces of your ifrastructure, such as your data ceter, storage, backup techology, ad etworkig cofiguratio, ca make a real differece i the optios you have available to build ito your disaster recovery pla. Ca your recovery team directly access your servers i the data ceter if they eed to? Do you have eough storage for your backups? Ca you architect eough redudacy ito your ifrastructure from the groud up to make it highly available? These are just some of the physical limitatios you eed to keep i mid as you desig your disaster recovery pla. Documetig ad Implemetig the Disaster Recovery Desig Oce you ve idetified the iputs, requiremets, ad parameters of your pla s desig, you ca move o to the fu part: puttig it ito writig ad icorporatig its elemets ito your system. This is where the rubber meets the road where you must explicitly state how your SharePoit eviromet is prepared for the declaratio of a disaster ad how it will be restored after such a evet. Thoroughly documet your pla ad store it i a accessible, visible, ad reliable locatio so it ca be quickly accessed by ayoe who eeds to review, revise, or execute it. Tip: If your SharePoit disaster recovery strategy icludes oe or more alterate data ceters or facilities, your recovery pla ad ay associated documetatio should be replicated to those facilities to esure that they are up to date ad available i the evet of a disaster. Remember, there s always a chace that the author of the pla (you) is ot goig to be the perso who actually executes it, so make sure the pla cotais all the iformatio ad istructios required to execute it eve if the reader is t itimately familiar with the pla. The recovery pla should clearly state ay assumptios it makes about the executor ad that perso s kowledge of SharePoit ad related systems. Acquirig Resources Oce you uderstad your farm s recovery targets ad have a appropriate disaster recovery topology, you ca start reviewig your available resources ad establishig the assets eeded to provide or expad your disaster pla. You ca also defie the resources your pla requires if a disaster is declared ad you eed to execute your pla. Obviously, it pays to have those items o had before you actually eed them so you ca begi to satisfy the requiremets of the pla as quickly as possible. The followig list outlies the major resource areas you should review for your SharePoit eviromet ad its disaster recovery pla: Determie your physical requiremets ad resources. As has already bee metioed, your disaster recovery pla probably idetifies some specific pieces of required hardware ad

36 Chapter 2 SharePoit Disaster Recovery Desig ad Implemetatio 19 ifrastructure. Whether the pla s requiremets iclude rack space i multiple data ceters, high-speed storage area etwork (SAN), hardware for hostig virtualized servers, or tape backup drives, you eed to eumerate these items as completely ad specifically as possible. Review your etwork requiremets ad usage, power cosumptio, available storage, ad redudat devices such as load-balacers ad Redudat Array of Idepedet (or Iexpesive) Disks (RAID) arrays. Acquire your hardware. Oce you kow what you eed, make sure you have it o had whe you eed it. Do t put this off for a raiy day or the ext fiscal year. Disasters do t happe whe it s coveiet. You ca t afford to lose millios i busiess ad productivity because you saved thousads waitig to procure the hardware required by your disaster recovery pla. Acquire ad licese your software. If you have a failover farm, make sure to secure the proper software ad licesig for that additioal farm to stay i full compliace with your providers. Store copies of ay required software or media i a locatio (or locatios) that s accessible i the evet of a disaster. Work closely with your software maufacturer s licesig represetative. Explai exactly how you re usig the software, because the represetative ofte has special provisios (at lower price poits) for software ruig i a failover eviromet. Review your depedet services. Most SharePoit istallatios deped heavily o Active Directory (AD) for user autheticatio, ot to metio service accouts ad admiistrative access to servers. Closely examie the disaster recovery plas for your eviromet s AD domais, Domai Name Services (DNS), Dyamic Host Cofiguratio Protocol (DHCP) services, Simple Mail Trasfer Protocol (SMTP) services, ad all other services that your SharePoit eviromet depeds o. If these service depedecies have RPO or RTO targets that are out of aligmet with those that your SharePoit eviromet has idetified, you might eed to make alterate arragemets ad sped more moey. Establishig a Disaster Recovery Baselie Baselies determie a desired cofiguratio or setup for a give system at a specific poit i time ad are used as the basis for compariso for subsequet activities i ad chages to that system. Establishig a baselie for your SharePoit farm allows you to solidify a specific cofiguratio poit ad quality of service that your disaster recovery pla should strive to retur the system to after a catastrophe. Baseliig your system may ot be required for your orgaizatio, but doig so gives you a defied target for success ad goals that you ca drive your pla at. You ca also repeat the process at regular itervals, allowig you to quatify how your system has grow ad chaged over time, which ca also provide you with valuable data for future updates to your To- Be list. Regardless of whether you baselie your system, you should strive to have a complete picture of its curret state ad how compatible that state is with your disaster recovery pla.

37 20 SharePoit 2010 Disaster Recovery Guide Documetig Your Procedures for a Outage Up util ow, most of this chapter has focused o the items ad details eeded for a SharePoit eviromet s disaster recovery pla to establish the best positio possible to deal with the declaratio of a disaster. Now this chapter turs its attetio to some best practices for actually writig the pla ad recordig it i a cosistet ad cotrolled maer. This is importat because the pla must be uderstadable ad complete. Its audiece is likely to be uder a great deal of pressure whe usig it ad wo t have time to spare tryig to decipher a dese, ieffective documet. Followig Published Stadards for Writig If your orgaizatio already has a commo set of stadards for official techical documets, your disaster recovery pla should follow them. If ot, it may be worth the effort to establish them as part of this process. Whe you re writig a documet, it is t eough to simply outlie the steps a executor should take to complete a process. A complete techical documet should cotai several commo types of iformatio, icludig but ot limited to these: Ivolved parties. Lists the people associated with the documet, such as its author/ower, reviewer(s), ad approver(s) Versio ad revisio history. Details the documet s chages over time Effective date. Records the date that the documet became available for use Roles, resposibilities, ad capabilities. Icludes a list of the positios that eed to be filled to execute the documet s istructios, the resposibilities for each of those positios, ad the skills a resource must have to fill a positio Audiece. Defies who the documet is iteded for Purpose. Explais what purpose the documet should be used for Scope. Defies what s i scope ad out of scope for the documet Covered systems. Lists the systems or groups that the documet applies to Glossary of terms. Defies commo termiology used i the documet Prerequisites ad depedecies. Icludes ay activities or systems that must be completed or i place prior to the documet s executio Assumptios. Details the assumptios the documet makes Primary cotet. Icludes the istructios ad procedures the documet is iteded to cover Refereces. Lists iformatio, documets, or people exteral to the documet that ca be cosulted for additioal iformatio Traiig. Explais how idividuals should be traied o the documet s cotet ad procedures

38 Chapter 2 SharePoit Disaster Recovery Desig ad Implemetatio 21 Verifyig Cotet Oce you ve completed your disaster recovery pla, have a third party review ad verify it. If you do t, you risk allowig icosistecies, omissios, or errors to remai i the documet that could directly impact the success of a recovery operatio. Cosider this book as a example. Every page ad every word i it has bee reviewed, tested, ad verified by at least two separate parties. A copy editor checked it for grammatical cosistecy ad proficiecy, ad a techical editor checked the techical statemets, assertios, walk-throughs, ad cotet writte. No matter how much authors check their ow work, havig outside reviewers drastically improves the quality ad accuracy of a author s output. No disaster recovery pla should be allowed to stad without beig tested ad verified before it s cosidered complete; otherwise, you chace itroducig additioal, avoidable risk ito your disaster recovery activities. Lowerig the Impact of Recovery Take whatever precautios you ca to lower the impact of your recovery strategy o your Share- Poit eviromet ad its users. These steps will vary depedig o your situatio, but here are two importat areas to keep i mid that ca make the recovery process go much more smoothly: Securig your crucial disaster recovery resources. The eed for a secure, cetralized store for your software istallers, licese keys, ad other associated bits has already bee metioed, but it bears repeatig. Esure that your disaster recovery persoel ca access this storage locatio, ad make sure that its cotets are backed up ad potetially replicated o a regular basis. If your orgaizatio lacks a formal disaster recovery departmet or group, appoit a specific perso with the resposibility of maitaiig that store ad keepig it curret. Idetify a backup for that perso or group i case the primary is uavailable whe a disaster is declared. Idetifyig what to secure. What items, such as service accout idetities ad passwords, software licese keys, or data ceter access, should be secured ad uavailable to public access? What items should be commoly available to all resources? Review your system s assets ad the security aroud them to make sure that you are properly balacig your assets safety measures agaist the eed to access them quickly. Tip: As metioed i Chapter 1, certai types of privileged cofiguratio data are typically stored separately from other types of data. For cofiguratio data that is deemed secure ad stored separately, be sure that your disaster recovery pla idetifies how (ad from whom) such iformatio should be recovered if a disaster is declared. Defiig the Commuicatio Pla Your disaster recovery pla should also iclude a pla for commuicatig iformatio about the declared outage to everyoe associated with your SharePoit eviromet so that you re

39 22 SharePoit 2010 Disaster Recovery Guide presetig a uiform, cosistet, ad iformative frot to those costituets. The pla should idetify the various players ad roles i the recovery actio, such as data ceter techicias, database admiistrators, maagemet, quality assurace, ed user advocates, ad ed users i geeral. It should also detail the maer i which these various players should be cotacted, who should maage ad coordiate the commuicatio effort, ad the approvals required before a message ca be set. I additio, the pla should iform key persoel of how they ca obtai iformatio o their ow, via sources such as coferece calls, Web pages, ad phoe trees. It may also be beeficial to desigate a specific meetig area that the team ca use i perpetuity util the actio is completed so that the team always uses a cosistet locatio. Make sure that all key persoel i a recovery actio are idetified ad assiged specific roles to avoid gaps i kowledge ad argumets over areas of resposibility. Determiig Success The last thig your SharePoit disaster recovery pla must provide is a coheret, cocrete, agreed-upo list of criteria for a successful recovery. As stated earlier i this chapter, this list is ofte derived directly from the list of recovery targets. Defie the terms of a successful recovery before you attempt to coduct oe so that there are specific goals your team ca drive toward ad a poit where you ca declare victory. Keep your busiess users eeds i mid durig this process. As discussed previously, it does little good to deliver a system that may be fully recovered from a techical stadpoit but does ot allow busiess users to get their work doe. The success criteria ad associated coditios must be agreed upo by all stakeholders i your SharePoit eviromet ad with regard to the recovery targets that the BIA idetified. Your pla should also idetify a perso or group that is resposible for verifyig that these criteria have bee met ad approvig the completed recovery effort. Tip: You may fid it worthwhile to explicitly iclude a baselie for your SharePoit eviromet withi your disaster recovery pla ad use it as a bechmark for a successful recovery. This allows you to solidify a specific cofiguratio ad quality of service for your system that your disaster recovery pla should strive to retur the system to after a catastrophe, rather tha a assorted list of recovery targets. Coclusio Creatig a useful, effective disaster recovery pla ad documetig it properly is oe of the most importat aspects of a successful disaster recovery strategy. Documetatio is t oe of the more iterestig or excitig thigs that a IT admiistrator ca be tasked with, but it certaily is oe of the most crucial. Hopefully this chapter has give you a jump-start o the process. The goal is for you to use the recommedatios ad best practices described i this chapter as a startig poit for your orgaizatio s SharePoit disaster recovery pla. Do t forget that what

40 Chapter 2 SharePoit Disaster Recovery Desig ad Implemetatio 23 has bee preseted may ot cover everythig that your team eeds to meet the uique requiremets of your SharePoit eviromet. Also keep i mid that your pla should, at a miimum, address all the cocepts this chapter has itroduced. Oce you have developed your disaster recovery pla, the bad ews is that you re still ot doe. The good ews is that Chapter 3, SharePoit Disaster Recovery Testig ad Maiteace, walks you through the last steps of the process. Now that you ve leared about the importace of a effective disaster recovery pla ad what goes ito it, you should be able to aswer the followig questios about a pla s capabilities. You ca fid the aswers to these questios i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at 1. What are recovery targets? 2. What are some items to cosider whe evaluatig what compoets of your SharePoit eviromet to restore? 3. What are some of the ways your orgaizatio s RTOs ad RPOs ca impact the desig of your disaster recovery pla? 4. What are some examples of resources that must be acquired or provisioed as part of your disaster recovery pla? 5. How do you kow whe your disaster recovery pla has bee completely executed?

41 This page itetioally left blak

42 3 SharePoit Disaster Recovery Testig ad Maiteace I This Chapter Plaig Your Test Coductig the Test Performig Ogoig Maiteace of Your Disaster Recovery Pla Hopefully it goes without sayig that the cotet covered i this chapter is the ext logical step i your disaster recovery plaig process: testig ad maitaiig your pla. These items are atural ad importat compoets of ay iformatio techology (IT) project or process, but they re all too ofte give little attetio or resources. Give the potetial importace of your SharePoit eviromet ad its cotets, you ca drastically icrease your risk factor ad decrease the viability of your system if you do t adequately test ad sustai your disaster recovery pla. Obviously, these two items ca occur at differet stages i the life cycle of your disaster recovery process, but they re related. Most otably, the first maiteace activities of your pla are likely goig to happe after you coduct its first test. Testig your pla should produce several lessos leared, valuable data, ad ecessary modificatios. These aturally lead you ito the maiteace phase of the process. Likewise, as you cotiue ogoig maiteace for your pla, you should re-execute your tests to validate all the chages that you ve made to the pla. Plaig Your Test The quality of the testig you do for your disaster recovery pla ca be just as crucial to the success of your pla as the quality of its desig ad cotets. If you do t coduct a effective test of your pla, you do t have a comprehesive uderstadig of how it will be applied ad utilized if a disaster is declared ivolvig your SharePoit eviromet. Testig is the best way to begi idetifyig potetial bottleecks, weakesses, ad depedecies that you may ot have cosidered durig the desig process. Testig also provides your team with a outstadig traiig mechaism. Through executio of the pla, team members are developig a deeper uderstadig of the pla ad gaiig realistic experiece with it. Testig also helps you to estimate 25

43 26 SharePoit 2010 Disaster Recovery Guide your ability to meet your recovery time objective (RTO) ad recovery poit objective (RPO) goals, which are of paramout importace to the viability of the disaster recovery pla. Wheever possible, coduct disaster recovery testig for your SharePoit eviromet withi the cotext of testig your orgaizatio s overall busiess cotiuity pla (BCP). Give the iterdepedecies betwee techical systems such as SharePoit ad the busiess users who work with them, most of the time it is t sufficiet to simply test your disaster recovery pla i a vacuum. You eed to kow how your desig impacts the rest of the BCP, ay cosequeces the BCP may have for your recovery plas, ad ay other systems i your orgaizatio that deped o the restoratio of the SharePoit eviromet for their ow success. This iformatio lets you examie your commuicatio pla ad its viability, ot to metio allows busiess users to verify that their expectatios ad strategies ivolvig the BCP ad your SharePoit eviromet are accurate ad realistic. If your testig efforts do t i some way ivolve stakeholders or resources from the busiess side of your orgaizatio, you should at a miimum covey the results of your testig effort so these key people are iformed of your fidigs. Defiig the Scope of Your Outage The first step of defiig how to create a outage i your SharePoit eviromet for purposes of testig is to determie the scope of that outage. As with ay type of test or activity, the value of your test results is based o how successfully the test covers the key aspects of your system ad assesses the effectiveess of your disaster recovery pla. Ruig a test that does t impact SharePoit or is t likely to actually occur i the real world is t a productive use of your time ad resources. The followig list outlies some of the questios you should be askig yourself as you determie what your disaster recovery test will ecompass: What are the most likely types of outages your system may experiece? If your SharePoit eviromet cotais mostly read-oly cotet, there may be little reaso to test the retrieval of cotet that was accidetally deleted by ed users. If your servers are located i a area of the world proe to certai types of weather patters or atural disasters (torados, hurricaes, earthquakes, ad so o), does it make sese to simulate oe of those evets i your test? What are your most valuable recovery targets? Your test should cofirm your pla s ability to restore your system s most importat recovery targets. These are likely the items your busiess users will be lookig for first, ad your pla must be able to brig them back successfully. What items have miimal RTOs ad RPOs? If you have little time to brig back a resource or eed to brig back a resource to a recet state, it s imperative that you test ad verify your ability to meet those requiremets. What are your most vulerable recovery targets? If your SharePoit farm has compoets that are more likely tha others to be impacted by a outage, such as a WAN coectio or

44 Chapter 3 SharePoit Disaster Recovery Testig ad Maiteace 27 Iteret-facig servers outside your firewall, you should exercise them durig the disaster test. What resources are available for testig? There may be costraits placed o your test by the resources you have available to execute it with. If your productio SharePoit farm cotais load-balaced Web frot-ed (WFE) servers but your test eviromet does t, you wo t be able to test that high availability aspect of your disaster recovery pla. This evaluatio should also iclude resources exteral to your SharePoit eviromet, such as busiess represetatives, data ceter admiistrators, or storage area etwork (SAN) capacity available to your servers. What compoets or depedet systems i your SharePoit eviromet are govered by disaster recovery plas other tha your ow? Agai, cosider testig your pla as part of testig your orgaizatio s overall BCP. If you are testig idepedetly of the BCP, your pla may still have depedecies o other plas that you eed to examie. I particular, you should be aware of ay service-oly farms or published Service Applicatios that your SharePoit farm cosumes, because these may tie your recovery plas directly to plas that exist for oe or more additioal SharePoit eviromets. It may ot be ecessary to test these items, but you must verify that these exteral plas have bee tested or are assured by their owers to reduce the risk to your pla. Orgaizig Your Resources The obvious coclusio you may come to whe evaluatig how to test your SharePoit disaster recovery pla is that your test should, wheever possible, mirror the coditios, cofiguratios, ad resources foud i your productio eviromet as closely as possible. This is certaily oe way to approach your test, but you eed to determie if this is the most effective way to test your pla ad the most effective use of your resources. Review the requiremets ad desig of your pla, ad fid a approach for testig that is authetic ad challegig without wastig efforts or resources. Testig Your Systems Agai, your pla s RTO ad RPO goals play a importat role i decidig what systems or eviromets to use to coduct your test. If your SharePoit eviromet is desiged to deliver miimal or ear-zero RTO ad RPO outage widows, it s probably goig to ivolve multiple duplicate systems, such as replicated SharePoit farms i alterate data ceters, clustered databases, ad redudat storage. I this case, it may make more sese to actually coduct the test by leveragig these failover systems, eve though they re i a productio eviromet. This gives you a highly accurate profile of how your system will perform i a disaster by usig the actual systems that you ll eed to fuctio correctly whe somethig hits the fa. This is t to say that a duplicate testig eviromet is a poor solutio. Rather, the poit is to cosider the best testig solutio to give you the most accurate ad relevat data possible about how your pla, your SharePoit farm, its depedet systems, ad all the ivolved persoel will perform i

45 28 SharePoit 2010 Disaster Recovery Guide a disaster. If it makes the most sese for your orgaizatio to create a test eviromet for this activity, by all meas do so. But make sure that you thik about how your pla, its requiremets, ad its costituets are best tested, i additio to cosiderig your test s available resources ad budget. Also keep i mid that the physical resources your test requires are ot just limited to the Share- Poit eviromet eeded to ru your test. Just as your productio SharePoit eviromet most likely uses several other systems for moitorig, reportig, etworkig, ad other crucial capabilities, your test eviromet has equivalet depedecies to cosider. For example, if you rely o a moitorig system that geerates trouble tickets or pages resources whe a outage occurs, make sure that system is also moitorig the SharePoit farm hostig your test. But also cofigure the moitorig system so that productio resources are t assiged to hadle the evets geerated by your test system durig disaster recovery testig, to avoid cofusio ad service degradatio for the productio system. Testig Your People Wheever possible, make the test as authetic as possible, ot just i terms of the IT assets used, but also the team ivolved i the test. Assig participats to fill each of the key roles dictated by your disaster recovery pla so that the required actios, abilities, ad resposibilities of each role ca be assessed ad evaluated. Also iclude busiess owers or their represetatives i the test. This ca go a log way toward properly settig their expectatios i a outage ad ot oly give them a excellet uderstadig of the commuicatio they ca expect whe a outage occurs but show them the role(s) they play durig pla executio ad the overall recovery effort. Plaig for Losses Seriously cosider icorporatig certai losses of disaster recovery resources ad persoel i your test so that you ad your team ca uderstad how to overcome those challeges should somethig similar occur durig a actual outage. Who eeds to be iformed if the latest set of tape backups is corrupted ad a RPO target ca t be met? What if a database admiistrator is o vacatio durig a outage? Ca your pla still be executed to meet its criteria for success without the presece of key resources? By purposely buildig losses ito your test, you ca further idetify weakesses ad depedecies i your system. Verifyig Checklists ad Preparedess The iitial test of your system is also a excellet opportuity to verify or develop ay checklists that you may eed as job aids for the disaster recovery pla. Durig the plaig phase of ay project, it s ofte difficult to capture every ecessary activity dow to the smallest detail, but it becomes much more feasible to do so durig test executio. Creatig task ad resource lists ca make your persoel more effective durig a actual outage, improvig your disaster recovery team s efficiecy ad effectiveess while elimiatig commo mistakes ad missteps. It s also much easier to lear these lessos durig a test tha durig a actual disaster whe busiess owers are breathig dow your eck ad everythig has to be executed without surprises ad errors.

46 Chapter 3 SharePoit Disaster Recovery Testig ad Maiteace 29 Testig your disaster recovery pla with the people who are likely to execute it i a productio eviromet is a great traiig exercise for these resources ad ca idetify other areas for additioal improvemet. It also educates your parters ad service providers o what you ll be coutig o them for i the evet of a outage i terms of both services ad their delivery widows. Remember that your disaster recovery pla is likely goig to ecompass a group far larger tha just your SharePoit team. The more you ca do to esure the preparedess ad resposiveess of all parties ivolved i a recovery effort, the more effective the recovery effort is. Coductig the Test Remember that the more authetic your test is ad the more accurately it re-creates a outage of your SharePoit eviromet, the more value it gives you ad the more predictable ad effective your disaster recovery pla becomes. The test is t a excuse to icoveiece your persoel or make uecessary requests of your exteral service providers, but all participats should take the test seriously ad act as if it s a actual outage. With busiess represetatives ad otechical persoel from your orgaizatio participatig, it s eve more importat to take the exercise seriously to build their cofidece i your pla, your team s ability to execute it, ad the stability of your SharePoit eviromet i geeral. Ecouragig Commuicatio At all stages of the test, ecourage commuicatio amog the test s participats ad provide them with all the iformatio ecessary to fully participate i the test. This starts with the test s kickoff activities, where the participats are itroduced to the test SharePoit farm, assiged their roles withi it, iformed of the outage, ad provided with the specific details of the catastrophic evet that has occurred i the test eviromet. All participats must uderstad their role withi the test; otherwise, the test may ot be fully implemeted or worse, would be executed icorrectly. Throughout the test, the recovery team should have regular meetigs to commuicate status ad fidigs. The frequecy of meetigs ca follow the commuicatio requiremets of the disaster recovery pla, but you might eed to provide updates o a more cosistet basis as participats execute, lear, ad troubleshoot the pla. Record all the key fidigs, tips, issues, ad commuicatios made durig the test so that you ca review them oce the exercise is completed ad icorporate them ito the revised pla. Tip: Because recordig iformatio ad observatios durig a test ca take a sigificat amout of time, assig a ote-takig observer for each perso carryig out some part of the recovery pla. Takig this step esures that executio of the recovery pla is t slowed ad that the feedback gathered is objective i ature. It also ecourages recovery pla participats to stay focused o the work they re doig rather tha takig otes.

47 30 SharePoit 2010 Disaster Recovery Guide After the test has bee completed, you ca take several steps to gather further iformatio about it. Collect ay ad all otes that participats made durig their activities, ad survey all cotributors to collect geeral thoughts ad resposes about the test. Oce you ve gathered all the data, commuicate a summary ad fidigs report to all participats. Make sure that the persoel executig the test are give feedback o their work so they kow what they did well durig the test ad what they eed to work o ad improve i the evet of a actual disaster. Also icorporate the fidigs ito the disaster recovery pla; for more iformatio o maitaiig your pla, see the sectio Performig Ogoig Maiteace of Your Disaster Recovery Pla later i this chapter. Observig the Test I additio to the otes, thoughts, ad data geerated by the ote-takig observers assiged to each of the test s participats, it s importat to assig certai members of your team to observe the overall test as it progresses. These idepedet observers should especially be o the lookout for items that are ot addressed but eed to be added to the larger disaster recovery pla, differet streams of recovery that may coflict with oe aother, activities that have some depedecy o other activities, timig, or some other outside ifluece. You may fid that you re best served by assigig this task to team members closely familiar with the disaster recovery pla so they ca sped their time observig the test, as opposed to costatly referecig the pla to cofirm oe detail or aother. This esures that your less experieced team members are gettig more hads-o time with the pla to build their kowledge ad expertise. Validatig the Pla The ice thig about testig your disaster recovery pla is that it should already provide you with the criteria you eed to evaluate whether you passed. Your SharePoit eviromet s disaster recovery pla should ot oly defie the bechmarks ad goals you eed to meet for a successful recovery from a outage, but it should iform you of the RTO ad RPO goals you re required to meet to fully satisfy your busiess owers requiremets. Oce the test has completed, validate its output agaist these stadards ad determie how successful you were at meetig them. If you re uable to meet the RTO ad RPO requiremets of your pla, you ll eed to perform additioal aalysis to determie how to remedy that issue ad update the pla accordigly. Redesigig the Pla After you ve validated your test ad reviewed its output, you may eed to redesig your pla based o your fidigs. Although you ca t expect your disaster recovery pla to accout for every complicatio or calamity that may arise durig the recovery of your SharePoit farm, a effective test of your pla ofte results i some valuable iformatio ad chages to the pla. Your resposibility, oce the test is completed, is to refactor the pla based o those coclusios ad the retest it to verify the accuracy of your modificatios.

48 Chapter 3 SharePoit Disaster Recovery Testig ad Maiteace 31 Performig Ogoig Maiteace of Your Disaster Recovery Pla I life ad i IT admiistratio i particular, the oly costat is chage. Oe challegig aspect of creatig a disaster recovery pla is that the system you re desigig agaist is likely to go through frequet modificatios, eve durig the course of your desig process. It is ot ucommo that i as soo as six moths after your pla is completed ad approved, the system you desiged it for will have grow, matured, ad bee updated to the poit that the pla is o loger fully relevat. That s why it is t oly importat to write your pla i such a way that it ca be easily modified ad updated, but to re-evaluate ad update it o a regular basis to keep it i lie with the SharePoit eviromet it addresses. Aalyzig Your Systems: As-Is/To-Be Oe way to aticipate chages that may be required for your SharePoit disaster recovery pla is by creatig some key lists that track the curret ad future state of your eviromet. Orgaizatios are costatly evaluatig their IT systems to determie if they re able to meet their specific eeds ad lear what modificatios, additios, or subtractios they may make to them i the future. Ofte this aalysis is broke ito two sectios: As-Is ad To-Be. As-Is aalysis of a system examies the busiess s curret users, processes, ad data ad compares it to the existig IT system. This compariso is the used to evaluate how well the system serves the eeds ad actios of the busiess ad to establish a baselie for the future state of the system. The future state is defied i the To-Be aalysis. The To-Be list defies the visio for the busiess s IT systems of the future, prioritizes features ad fuctioality, ad establishes goals that upgrades should meet or exceed. A effective disaster recovery pla is desiged to meet the requiremets ad coditios set forth by the As-Is list of a orgaizatio while keepig a eye toward the state described by the To-Be list. A pla must ecompass the curret system s etire cofiguratio, workflows, ad data but also be flexible eough to either hadle or be modified to accommodate the projected future state of the system. If a disaster recovery pla ca t grow with your SharePoit farm as its role withi your orgaizatio grows, ad thus its IT footprit grows to match, it quickly loses its effectiveess. If your orgaizatio does t have official As-Is ad To-Be lists that iclude your SharePoit eviromet, cosider compilig these items before fializig your SharePoit disaster recovery pla. You eed to have a cocrete uderstadig of your system, its stregths ad weakesses, ad its projected future state to effectively kow what eeds to be preserved ad restored ad how that could yield chages to your disaster recovery pla i the comig years. Modifyig Your Pla I geeral, your orgaizatio should have procedures that gover the review ad update of approved documetatio so that all documets are evaluated o a regular basis (for example, every year) ad updated accordigly. You may fid that, based o how your SharePoit system

49 32 SharePoit 2010 Disaster Recovery Guide evolves ad grows, your disaster recovery pla requires more frequet care ad feedig. Take care to establish certai criteria that ca trigger a update to your pla, such as a major release for your system, the deploymet of ew hardware, or the istallatio of service packs or versio upgrades for your software. Whe you do modify the pla, create a ew versio of its documetatio so that you ca maitai ad track a history of its chages over time. Esure that the documet agai goes through a full review ad approval process so that all stakeholders are made aware of the chages that have occurred i the system ad the disaster recovery pla itself. Allowig the pla to gather dust while the state of your productio SharePoit system evolves presets a major risk to the pla s relevace ad effectiveess ad your ability to actually recover the system i a catastrophe. Tip: Specialized applicatios ad systems, such as SuGard s Livig Disaster Recovery Plaig System (LDRPS), exist to serve ad address the eeds of disaster recovery plaers. These applicatios ad systems ca greatly simplify the processes of disaster recovery documetatio, chage trackig, ad ogoig pla maiteace. If your orgaizatio cotais a group with formalized disaster recovery resposibility, check with them to see if you could or should be leveragig such a system for your SharePoit disaster recovery plaig purposes. If the decisio is i your hads, ivestigate the use of oe of these systems. It ca save time, effort, ad most importatly, cofusio particularly whe disaster strikes. Expectig ad Budgetig for Ogoig Maiteace To make chages to your disaster recovery pla, you eed to exped at least some resources i the form of the time ecessary to redesig the pla to meet the chagig eeds of your systems as well as ay additioal hardware or software that the redesiged pla may require. Be prepared for expeses beyod time if the scope of your SharePoit farm grows, because you ll likely require further physical resources such as expaded storage space or more servers, ot to metio the possibility of specialized backup ad restore software. All these items ca add defiitive costs to your budget that you may ot ecessarily aticipate oce the disaster recovery pla is i place, but you should expect them as part of your pla s ogoig maiteace. As ecoomic circumstaces fluctuate ad available budgets grow ad shrik, you must make sure that sufficiet resources are made available to support ogoig maiteace of the pla. Tip: The yearly cost of disaster recovery maiteace is ofte tied to the disaster recovery desig that is implemeted for a SharePoit farm. A best practice for most corporate SharePoit farm owers is to calculate ad budget for the cost of ogoig disaster recovery maiteace at the same time they prepare a capital asset request for the acquisitio of a SharePoit eviromet ad the iitial implemetatio of its disaster recovery strategy ad desig.

50 Chapter 3 SharePoit Disaster Recovery Testig ad Maiteace 33 Coclusio The worst thig you could do oce your disaster recovery pla is completed ad approved is to put it o a shelf ad forget it. As you have hopefully gleaed from this chapter, disaster recovery plaig is a process of cotiuous improvemet, ot a oe-time activity. Just as your users are costatly addig ew cotet, documets, tasks, ad more to your SharePoit sites, the system is growig with them, ad you eed to be cofidet that you ca recover your system i the evet of a disaster i spite of those chages. This may require some vigilace o your part, but there are ways that you ca alleviate this burde. Moitor your IT orgaizatio s chage cotrol process for updates, rollouts, or decommissioig activities that may impact your pla. If your orgaizatio does t have a defied chage cotrol process, implemet oe as soo as you ca. Although this process ca create overhead ad some extra work for your admiistrators, it provides a opportuity to review the importat chages that are beig made to your systems ad see how they ve chaged over time. Baseliig your SharePoit system o a regular basis ca also aid i the maiteace of your disaster recovery pla. Comparig a give baselie to the curret state of the system allows you to idetify chages ad additioal items that your pla may eed to address. It may be best to icorporate a system baselie ito your regularly scheduled or triggered maiteace activities for your pla to esure that it s happeig o a cosistet basis. Regardless of how you do it, treat your SharePoit eviromet s disaster recovery pla as a livig documet oe i a regular state of modificatio ad improvemet like a etry i a wiki, rather tha a static resource that chages less tha the Ecyclopedia Britaica. But remember, give the importace of your farm s disaster recovery pla, the quality ad accuracy of the iformatio i it should be created, reviewed, tested, ad approved more like that of the Ecyclopedia Britaica tha a wiki. Now that you ve see how to test ad maitai your SharePoit disaster recovery pla, you should be able to aswer the followig questios. You ca fid the aswers to these questios i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at What are some examples of resources that ca be removed from a test of your disaster recovery pla to check its effectiveess? 2. What are some of the expected outputs you should have oce a test of your pla is completed? 3. Explai the role that idepedet observers play durig a disaster recovery test? 4. Ca you describe some of the potetial risks of ot updatig your disaster recovery pla over time? 5. What s the differece betwee a As-Is ad a To-Be list?

51 This page itetioally left blak

52 4 SharePoit Disaster Recovery Best Practices I This Chapter Gettig to Kow Yourself Gettig the Right Tool(s) for the Job Puttig It All to Good Use Now that you have a firm groudig i ad uderstadig of the geeral cocepts of disaster recovery, it is time to start figurig out how to apply those cocepts to your SharePoit eviromet. This is where you are fially goig to get ito the techical aspects of your SharePoit disaster recovery solutio ad deal with the mechaics of protectig your SharePoit farm. The good ews is that this should be somewhat easier for you ow that you are thikig about the requiremets you eed to meet ad some of the resources that you should have available to satisfy those requiremets. The bad ews is that, as much as you would like oe, there is ot a sigle, oe-size-fits-all, magically hadle everythig solutio for SharePoit disaster recovery (or at least ot out of the box with the tools that come with SharePoit ad its associated platforms). The purpose of this chapter is to bridge the gap you may be oticig betwee geeral disaster recovery plaig ad solvig the techological pieces of the disaster recovery puzzle. Although there is o oe woderful tool for everyoe to use, you ca assemble your perfect SharePoit disaster recovery strategy oce you aswer a commo set of questios. As you read this book s subsequet chapters o the tools that are at had for protectig your SharePoit eviromet, bear i mid the cocers posed by this chapter ad the oes that come before it. As you read about disaster recovery tools ad techiques, cosider if ad how they pertai to you ad your eviromet. Every SharePoit eviromet s approach to disaster recovery is uique, ad addressig with ope eyes the questios ad cocers that are posed ultimately helps to lead you to the disaster recovery strategy that is right for you. 35

53 36 SharePoit 2010 Disaster Recovery Guide The visual examples provided i this chapter were geerated i a testig eviromet usig the followig platforms ad compoets. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 Developer Editio with Service Pack 1 (SP1; build ) Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 SharePoit. SharePoit Foudatio 2010 Release Cadidate 1 (build 4730) Gettig to Kow Yourself Oe of the reasos SharePoit has see almost uprecedeted adoptio by busiesses i recet years is its flexibility. Do you eed to allow your employees to easily collaborate o busiess documets? SharePoit ca do that. Do you eed to fid critical iformatio stored i a variety of formats ad locatios throughout your iformatio techology (IT) ifrastructure? Share- Poit ca do that. Do you eed a Web site that your cotet creators ca maitai ad maage without havig deep kowledge of HTML, CSS, or other Web programmig laguages? Share- Poit ca do it yet agai. But that flexibility is ot just limited to its fuctioality. You ca also deploy SharePoit s ifrastructure compoets ad services i a rage of cofiguratios to meet your specific eeds ad resources. You ca deploy SharePoit to somethig as simple as a sigle server ruig Widows Server 2008 Stadard Editio ad SQL Server Express 2008, all the way up to a global multifarm eviromet ruig Widows Server 2008 Eterprise ad SQL Server 2008 Eterprise. The iclusio of Service Applicatios, such as Project Server 2010 ad PerformacePoit 2010, ca also vastly chage the fuctioality, complexity, ad compositio of your SharePoit eviromet. Your SharePoit cofiguratio has a direct impact o how you pla your eviromet s protectio. You eed to take ito accout several aspects of that cofiguratio before you ca begi to fully flesh out the details of how you are goig to meet the requiremets of your disaster recovery pla ad stay withi the costraits you have idetified. The items i this sectio highlight several areas that you eed to examie i your SharePoit ifrastructure to help you make iformed decisios about the right way to protect it. Kow Your Scope As you begi to desig your SharePoit disaster recovery solutio, the first thig you eed to determie is the compoets or facets of the SharePoit farm you are actually goig to protect. This is the process that defies the scope of your disaster recovery solutio, but it s ot as simple as it may seem. It is ot just a matter of declarig a site collectio i your disaster recovery pla or decidig to omit a server from it. Yes, you should start by goig through somethig similar to

54 Chapter 4 SharePoit Disaster Recovery Best Practices 37 that to determie what s i ad what s out, but there s more to it tha that. Truly defiig the scope of your disaster recovery solutio meas that you kow what you are goig to cover, what pieces of your SharePoit eviromet are more importat tha others, what potetial risks your targets have, ad what your restored eviromet looks like followig recovery from a disaster. What Do You Need to Cover? This should be the easy part, or at least the most straightforward part of the process: defiig the pieces of your SharePoit eviromet that you must preserve i the evet of a disaster. All of it, right? As much as you may like to cover your etire eviromet, this may ot be the best course of actio or eve somethig that s ecessary. Idetify those items withi your eviromet that are missio-critical ad those that are ot. You should do a large part of this whe you establish your disaster recovery pla s recovery targets, but ofte that process focuses o SharePoit compoets ad cotet from the ed users perspective, ot from a IT or ifrastructure perspective. If you have ot established your disaster recovery pla s recovery targets, ow is the time to do so. Make sure to go back ad read the first three chapters of this book, because there is importat iformatio withi them about the importace of properly defiig your recovery targets. The ature of each of the recovery targets you idetify plays a critical role i uderstadig how you are goig to protect ad recover those same targets. Now is the time you eed to drill ito those targets ad uderstad the techical elemets ad depedecies i your eviromet that act to support ad keep those targets operatioal. The depedet systems ad techologies you idetify through this process become recovery targets themselves, ad the process of examiatio ad depedecy walkig cotiues with them. Whe followed to its logical coclusio, the process of tracig the chai of techical depedecies esures that you idetify all the elemets withi your eviromet that prop up or support the recovery targets origially specified. It is oly by addressig each of these items or techologies withi the disaster recovery pla that you esure that the pieces are i place to support the recovery of your origial SharePoit targets. How Is Your Eviromet Beig Used? The purpose of your SharePoit eviromet also impacts how you hadle it from a disaster recovery perspective, because SharePoit use cases ofte ivolve specialized compoets, platforms, ad ifrastructure to fuctio properly. I the software idustry, use case describes how you ca use a give tool or applicatio i a certai situatio. A large SharePoit Search eviromet may eed a specialized storage area etwork (SAN) with high disk iput/output (I/O) throughput for performace reasos. You eed to back up such a SAN differetly tha you would a hard drive directly attached to a server. A SharePoit extraet solutio is likely to use a security platform such as Microsoft s Uified Access Gateway (UAG) ad Threat Maagemet Gateway (TMG) products to autheticate users ad secure traffic commuicatig with SharePoit from outside the local etwork. You must restore a service such as this alog with SharePoit to fully retur the system to service. O the other had, you might ot eed

55 38 SharePoit 2010 Disaster Recovery Guide developmet or testig eviromets to be protected, because they do ot (or at least should ot) hold productio data ad cotet. Note: I the past, Microsoft had positioed TMG ad its predecessors (primarily the Iteret Security ad Acceleratio server product, or ISA) as its primary platform to secure iteral cotet whe cliets access it outside the local etwork, but that has recetly chaged. A few years ago, Microsoft purchased a compay called Whale, which offered a ehaced Web firewall ad reverse proxy product. Microsoft has tured that product ito the ew UAG offerig. (Iroically, the Whale product was built o top of Microsoft s ISA platform.) Now Microsoft is recommedig that TMG be a firewall as well as a Web proxy ad UAG take over the resposibility of securig ad ecryptig ed user traffic to SharePoit as well as other remote access fuctioality. TMG ca still be used for Share- Poit publishig i the curret release. What Are Your Priorities? What is the most importat thig i your SharePoit eviromet? What is the least importat? Do these items have the same recovery poit objectives (RPOs)? How about recovery time objectives (RTOs)? If they do t, should you sped the same amout of effort ad resources to protect both of those items i the same way? If they do, do you eed to reexamie these metrics ad adjust your disaster recovery pla accordigly? Kowig the highest value targets withi your eviromet is critical, because these are the items you eed to focus your protectio ad recovery efforts o above all else so you ca deliver the best possible solutio for your orgaizatio ad your users. Keep a Eye o Complexity Prioritizatio is a good way to make sure you are directig your resources ad efforts at the compoets that eed them most, but prioritizatio does come with a price. As you defie your priorities, exercise care to keep them from becomig too graular or arrowly focused. It is all too easy to itroduce uecessary complexity ito your disaster recovery solutio, which ca make your system difficult to maage ad easily lead to higher costs ad iaccuracies i the delivery of your solutio. Some complexity may be uavoidable due to busiess requiremets or costraits; i those situatios, it is still importat to ote ad allow for the risk it ca pose to the viability of your SharePoit disaster recovery solutio. What Do You Need to Restore? This might seem like a pretty simple questio, but avoid takig the aswer for grated. Although it might be easy to just say that you eed your collaboratio sites or your busiess itelligece portal restored i accordace with your RPO ad RTO targets, there s a great deal more that ca go ito recoverig those resources tha just restorig a sigle backup file. Take ito accout

56 Chapter 4 SharePoit Disaster Recovery Best Practices 39 the depedecies that are tied to your recovery targets, because it is highly likely that recovery from a disaster etails brigig those depedecies back olie to fully restore your critical SharePoit cotet. After you kow what you eed to restore, you ca accurately formulate a pla to preserve it. Kow Your Budget Oe of the most eye-opeig aspects of a comprehesive disaster recovery solutio ca be its price tag. Cost is a major cosideratio whe plaig how you are goig to protect your Share- Poit eviromet. Eve though the techical optios covered i the followig chapters are ofte available without purchasig additioal software liceses, you caot assume they are cheap to implemet. For example, cosider SQL Server 2008 s failover clusterig capability, a compellig compoet of SQL Server 2008 s Stadard ad Eterprise liceses. To use failover clusterig, you eed special hardware i the form of a SAN. This storage resource is ecessary so you ca share a sigle storage resource across the multiple member servers i the cluster; however, it does ot come cheaply. Although the umber of optios i this space is icreasig ad prices are decreasig, purchasig a SAN resource that is capable of providig the performace required to host Share- Poit s SQL Server database ca come at a cosiderable cost. Whe you reflect o failover clusterig, cosider costs such as these, ad evaluate them agaist your available budget. The ogoig cost of additioal storage to hold backup files, regardless of platform, is the most commo cost (ad oftetimes oe of the most sigificat oes) that you are goig to have to prepare for whe you thik about implemetig a SharePoit disaster recovery solutio. Whether your solutios employ tapes, disks, optical media, or other forms of storage, you must factor ito your budget the cost of the media ad the hardware eeded to leverage it. Defiig the cost of your disaster recovery solutio is a good exercise ad aother importat reaso why disaster recovery plaig eeds to ivolve both the techical ad busiess stakeholders i your orgaizatio. Every party with a dog i the hut eeds to uderstad how much it costs to deliver a disaster recovery solutio ad be able to properly reevaluate ad prioritize their requiremets to fit them ito the budget available for the solutio. This is usually ot a easy or ejoyable activity, but it is a ecessary oe oetheless. Kow Your Ifrastructure To a ed user, SharePoit is a great deal like most other Web sites; as log as you kow the correct URL ad have the right to access the site, it opes i your Web browser just like ay other Web page ad presets you with a familiar user experiece. Just like ay other Web site, there is ofte a great deal more goig o behid the scees to sed those SharePoit pages to your Web browser. SharePoit 2010 has specific software eeds (Widows Server 2008, IIS 7, SQL Server) ad cosiderable hardware eeds (high-performace processors, a great deal of RAM, high-capacity ad high-performace storage, ad a high badwidth etwork), ot to metio other optioal elemets such as load balacers, firewalls, ativirus protectio, custom

57 40 SharePoit 2010 Disaster Recovery Guide code, ad much more. Your SharePoit eviromet s ifrastructure ad the details of its cofiguratio directly affect how you should properly protect SharePoit. What Do You Have? As a geeral IT best practice, you should have a ivetory of your eviromet s curret ifrastructure. You should also be documetig the cofiguratio of the eviromet. If you are ot yet doig these thigs, it is ever too late to start. This data is ivaluable i a disaster. Without it, you have little hope of accurately re-creatig the proper eviromet i which to restore service. This documetatio also affects how you pla your disaster recovery strategy, because differet types of resources you seek to protect ofte require differet solutios. Oce you uderstad what you have, you ca effectively begi to prepare to safeguard it agaist the worst. I additio, you eed to kow how much cotet you are goig to protect withi your Share- Poit eviromet. You eed to kow how much cotet you curretly have i your farm, but you also eed to kow how much is goig to be goig ito it i the future. This ca ifluece your choice of tools to protect your eviromet with, because some protectio optios are poorly suited for larger eviromets. For example, Microsoft recommeds agaist usig site collectio backups (via PowerShell or Cetral Admiistratio) with site collectios larger tha 85GB. Uderstadig these types of limitatios, as well as the amouts ad types of data you ited to protect, permits you to make iformed disaster recovery plaig decisios. Microsoft has doe extesive testig of SharePoit s out-of-the-box backup ad recovery tools. It has foud that the tools have a much higher rate of failure oce certai sizig boudaries, such as the oe metioed earlier, are crossed. If you pla to use SharePoit s PowerShell cmdlets or the Cetral Admiistratio site for backup or restore activities, keep a close eye o the size of your farm, its cotet, ad its site collectios as they grow to esure that they are stayig withi Microsoft s sizig boudaries for those SharePoit 2010 tools. If they outgrow the tools, you eed to be prepared to cosider other optios or accept a much greater risk to the viability of your backup operatios over time. For more iformatio o this subject, see Microsoft s Backup ad Recovery Overview page i TechNet at library/ee aspx. For specifics o those sizig boudaries, see the Pla for Backup ad Recovery page o TechNet at What Ca You Do with What You Have? Be as specific as possible whe populatig your ivetory; small details ca have a large impact o how you ca cofigure your SharePoit disaster recovery solutio. You caot expect that it is sufficiet to kow that your eviromet is usig SQL Server, give the complexity Microsoft ad other vedors have built ito their licesig ad provisioig models. Take SQL Server 2008 s ability to compress backup files, for example. This is a desirable piece of fuctioality that ca save you a great deal of moey o storage costs, but you have to kow exactly what release of SQL Server you are usig because it is ot a feature that is globally available i all liceses for SQL Server. Whe it was itroduced, it was available oly with the Eterprise

58 Chapter 4 SharePoit Disaster Recovery Best Practices 41 Editio licese for SQL Server 2008 ad was ot icluded i ay editio of SQL Server Now, with the recet release of SQL Server 2008 R2, backup compressio is available i all licesed versios. This is just oe example of how importat it ca be to kow exactly what you have i your eviromet ad what those resources are capable of; thaks to the complexity of SharePoit ad its supportig platforms, several cases like this ca be a issue if you make icorrect assumptios about the capabilities of your resources. You eed to kow what you caot or should ot do with your resources. Do your storage systems have the throughput (disk throughput is measured i iput/output per secod, or IOPS) ecessary to restore a backup to a protected system fast eough to meet your RTO targets? Does Microsoft support the tools or platforms you are usig i your eviromet? If you do ot kow the aswers to these types of questios, you are puttig your disaster recovery solutio ad your overall SharePoit eviromet at risk. Cosider this from the perspective of oe of the IT idustry s most valuable ad recet techological developmets: server virtualizatio. Virtualizatio is the practice of buildig a complete computer eviromet o top of a software platform istead of a hardware oe, allowig for multiple virtual computers to be ru o a sigle physical host. Virtualizatio allows for a full server eviromet to be abstracted ito a virtual machie (VM) cotaied i a set of files o the storage system of its host; may of the moder server virtualizatio platforms (such as VMware s vsphere ad Microsoft s Hyper-V) ca easily copy ad trasfer those files betwee hosts. This practice, ofte referred to simply as copyig a VM, is regularly touted as a excellet backup/restore solutio. It offers ease of use ad a great deal of flexibility for restoratio because the VM abstracts away so much of the hardware layer. Virtualizatio gives a IT orgaizatio flexibility i how it ca deploy its resources; ofte it ca provide a defiite retur o ivestmet by allowig the orgaizatio to truly optimize its hardware across all its platforms. SharePoit rus well whe virtualized (i most circumstaces; it does ot do well i use cases or server roles requirig high IOPS, such as database servers), ad Microsoft supports it o multiple virtualizatio platforms. But the use of VM copies as a disaster recovery solutio is ot exactly such a ecouragig or cut-ad-dried story. Why is that? VM copies are pretty straightforward, right? You make a copy of those VM files o the host server s file system, store them i a remote locatio, ad i the evet of a disaster just move them to a fuctioal server ad tur them back o. That s how it works for most platforms, but you have to remember that SharePoit s architecture makes it a differet beast, especially i a multiserver farm sceario. Part of the problem with usig VM copies stems from SharePoit s use of timer jobs to ru scheduled activities ad fuctios throughout the farm ad o idividual servers. SharePoit does ot allow you to easily prevet timer jobs from startig, at least ot without completely shuttig dow a server, so the chaces of beig able to start ad stop a VM copy activity with all of a server s SharePoit timer jobs maitaiig the same status throughout are low over time. This lack of cosistecy i creatig VM copies of your SharePoit servers itroduces a uacceptable level of risk from the perspective of protectig your SharePoit servers. As a extreme

59 42 SharePoit 2010 Disaster Recovery Guide example, cosider the case of a SharePoit server that is copied while a service pack is beig istalled. Uder such circumstaces, the server is i a icosistet state. If the VM copy that is geerated from this server is brought olie, will the service pack istallatio cotiue? Will the server VM eve boot? The result is ucertai due to the icosistet state of the server whe the copy is created. The compaio to this problem is oe of overall farm cosistecy, at least for virtualized multiserver SharePoit eviromets. Not oly are there frequet activities ruig withi a give SharePoit server, but that same server is i almost costat commuicatio with the other SharePoit servers i the farm as well as the SQL Server istace hostig the farm s databases. I fact, SharePoit is so closely tied to its databases that it caot fuctio without them; they are the glue that holds a farm together. SharePoit s servers are costatly sedig ad receivig data to ad from its databases. For a set of farm VMs to fuctio, those VMs must be created (or copied) for the etire farm at the same time ad while the farm is i a cosistet state. Failig to copy all members of the farm at the same time ad i a cosistet state itroduces risk should you eed to restore those farm members. Now, this is ot to say that you caot use VM copies to capture a SharePoit farm for disaster recovery purposes. Microsoft does recommed oe solutio: shuttig dow the target server prior to copyig it. This esures that there are o ruig processes or etwork traffic that may ot be completely captured because the server is ot active durig the operatio. But is it worth it? This approach requires that you either cofigure all the servers i your farm to be highly available so the target server s fuctioality ca be delivered by aother server i the farm or schedule regular outages durig which copies ca be created. Neither may be a attractive optio, ad you must carefully weigh the implicatios for your IT orgaizatio as well as your ed users before you decide to go with VM copies. Ultimately, how you itegrate virtualizatio ito your SharePoit eviromet ad its disaster recovery solutio is up to you. If you are plaig o virtualizig your SharePoit servers, you eed to strive to stay up to date o iformatio from Microsoft ad the SharePoit commuity about usig virtualizatio as a disaster recovery solutio. Do t assume that VM copies are all you eed to protect your eviromet. At the same time, do t fall ito the trap of thikig that thigs wo t chage. How Does the Eviromet Chage? From the momet you decide to implemet SharePoit i your orgaizatio, chage is occurrig. From the time you start deployig servers i a dataceter to the momet the first user opes a SharePoit site i his browser ad well beyod, chages are occurrig that you have to track. Your disaster recovery solutio eeds to be able to hadle those chages ad adapt to accout for chages it caot hadle. Adoptio is a major area of cocer for ayoe who implemets SharePoit. Although most of the focus is directed toward ecouragig adoptio, the growth of your system is the type of

60 Chapter 4 SharePoit Disaster Recovery Best Practices 43 chage most likely to affect your disaster recovery solutio. For example, your RPO ad RTO targets may alter to reflect a icreased depedece o SharePoit by your users. At the same time, greater usage ofte results i greater storage use ad related demads. Your disaster recovery solutio eeds to be flexible ad extedable to accout for these types of potetial chages. That s ot all. A major key to a high-quality IT eviromet is effective chage maagemet. Chage maagemet is the process of chagig a system with oversight ad cotrol, as well as i-depth documetatio ad commuicatio. I ay IT system, just as i life i geeral, chage is ievitable. It is also somethig you must maage to prevet your IT ifrastructure from becomig umaageable. It does ot matter if you are the oly member i your IT orgaizatio or if you are a member of a large IT departmet; you must kow about the chages that are beig made ad documet them. Properly documetig your chages is crucial whe it comes to disaster recovery; if you do ot kow what was doe to get your system to its curret state, how ca you possibly kow how to restore it to that state if calamity should strike? Implemetig a chage maagemet process is somethig you should have i place for your IT eviromet i geeral, but it is absolutely essetial if you ited to take disaster recovery seriously. Kow Your Curret State Oce you implemet a disaster recovery solutio, do t thik that your work is doe. As already metioed i Chapter 3, SharePoit Disaser Recovery Testig ad Maiteace, there is a great deal of ogoig maiteace ad testig you eed to pla o performig for your disaster recovery solutio oce you have put it ito practice to esure its log-term viability. I additio to those activities, you eed to stay o top of ay supportig ifrastructure tied to the disaster recovery solutio to make sure that it remais healthy ad is fuctioig properly. Regardless of how you decide to protect your SharePoit eviromet, there are certai aspects of it that you should always be moitorig to have a accurate uderstadig of its curret state. I geeral, strive to have a moitorig solutio i place for your SharePoit eviromet, whether it is Microsoft s System Ceter Operatios Maager, a third-party product such as the Nimsoft Moitorig Solutio, a ope-source platform built o top of a tool like Cacti, or simply your ow custom scripts usig the Widows evet logs ad Widows Performace Moitor. Moitorig is a essetial facet of a stable IT eviromet, ad it should keep admiistrators iformed of issues withi their systems before users kow about them. It also permits admiistrators to be proactive istead of reactive by idetifyig treds ad patters withi the eviromet that should be addressed before they become troublesome issues. If you do have a moitorig solutio i your eviromet, make sure it is cofigured to ecompass the compoets of your disaster recovery solutio so that the health ad performace of your disaster recovery ifrastructure are tracked alog with the rest of your systems.

61 44 SharePoit 2010 Disaster Recovery Guide Gettig the Right Tool(s) for the Job Let s be hoest. Workig i the IT idustry does ot (usually) require the same kid of physical exertio that is required i more traditioal fields such as costructio or farmig. There are parallels that you ca draw betwee these diverse disciplies, though, especially i the area of toolig. Regardless of whether you get your hads dirty or squit your eyes at a LCD scree all day log, your job is much more difficult if you do t have the right tool for the job at had. Does a carpeter use the same saw for every kid of wood he s cuttig or every kid of cut he makes? Does a farmer use a garde spade to plat 40 acres of seed cor? No, ad these people go out of their way to make sure they avoid situatios i which they are forced to make do with subpar solutios. It stads to reaso that to effectively protect your SharePoit eviromet i case of a disaster, you eed to have the best possible tools o had to meet your recovery objectives. Whe cosiderig how to protect your SharePoit eviromet with a disaster recovery solutio, realize that o oe tool or process is goig to address all requiremets ad recovery targets. Be prepared to implemet a tool or strategy to back up your critical SharePoit cotet. The approach you select eeds to fit ito a overall disaster recovery pla ot take the place of it. Although the SharePoit platform comes with a set of backup ad restore tools, these tools address oly a subset of the full rage of disaster recovery cocers. These tools also come with their ow uique set of idiosycrasies, limitatios, ad problems that ca directly impact whe ad how they are used i the evet of a disaster. Remember: it is just as importat to kow what your tool or strategy caot do as what it ca do. The harsh reality of SharePoit s depedece o other platforms, such as SQL Server ad Active Directory (AD), is that you still have a great deal of work ahead of you to guaratee full disaster recovery coverage i your eviromet. It is equally importat to remember that you do ot have to pick just oe tool for the job; there is othig wrog with usig multiple tools to idepedetly protect your eviromet redudatly, especially whe those multiple tools allow you to cover gaps i your solutio that a sigle tool may expose. What Does the Tool Cover? You absolutely have to kow what a tool ca back up ad restore withi your eviromet. Does it back up your search idex? Does it back up customizatios that have bee deployed to the farm? Does it target SharePoit specifically, or does it protect SharePoit by protectig its supportig systems, such as Active Directory ad SQL Server? Aswer these types of questios thoroughly, because you do t wat to make assumptios about a tool s capabilities oly to fid out the hard way that you were wrog. Graularity Whe you re establishig your recovery targets, make sure to carefully establish the smallest uit withi your SharePoit eviromet that you are expected to protect ad restore withi a give

62 Chapter 4 SharePoit Disaster Recovery Best Practices 45 amout of time. The more arrowly ad graularly you defie your targets, the more importat it becomes to fid the right tool that is capable of providig that graularity. If you eed to be able to restore idividual documets i a library to a prior state, you eed to kow if the tool you re goig to use ca do that automatically for you or if you eed to take additioal maual steps to make it happe. May third-party products offer item-level restores, but with Share- Poit s out-of-the-box tools, you re still goig to have to take some maual steps to do it. If you have graular recovery targets, make sure that your choice of tool is able to be that graular or you have processes i place to fill the gaps left by the tool. How Does the Tool Provide That Coverage? A corollary to kowig what a specific tool ca cover withi your SharePoit eviromet is the uderstadig of how it provides that coverage. More succictly, how does it work? Does it use Microsoft s Volume Shadow Copy services or SharePoit s ow backup ad restore applicatio programmig iterfaces (APIs) to back up your farm? Does it require additioal hardware, software, or other resources to deliver o its promises? Additioal tool requiremets ad depedecies ca add a great deal more cost to your overall solutio if you are ot aware of them durig the plaig stages. Just as Olympic athletes eed to kow exactly what goes ito the food they are eatig or mechaics examie every ut, bolt, fluid, ad strut they use i a high-performace racig machie, you have to uderstad how your chose tool is goig to protect your SharePoit eviromet. What access rights does it eed, ad how do those requiremets impact ot oly SharePoit, but the rest of your busiess s eviromet? Ca it schedule backup operatios? Is it a easy tool to use, or does it require extesive traiig for your admiistrators to operate? You ca ever ask too may questios about the tools you decide to use as part of your SharePoit disaster recovery solutio, because a lack of uderstadig about them ca lead to dagerous assumptios ad a icreased level of risk to your solutio. What Does t the Tool Cover? It may be eve more importat to uderstad what a give SharePoit backup ad restore tool caot do tha what it ca do. Agai, makig icorrect assumptios about the capabilities of your tools ca have disastrous effects if those assumptios are ot revealed as false util you eed the tool for recovery. A tool s iability to cover oe aspect or aother of your SharePoit eviromet is ot ecessarily the ed of the world There is o rule that says you have to use oly oe device to meet all your eeds. Usig multiple tools is fie as log as you uderstad that it does icrease both the complexity of your solutio ad the umber of places i your solutio where somethig ca go wrog. This meas you eed to be especially careful i comprehesively traiig your staff o the use of all tools. You should also implemet a moitorig solutio that ca cover each tool, report o its status, ad alert you if somethig goes wrog with oe of them.

63 46 SharePoit 2010 Disaster Recovery Guide Ca the Tool Meet Your RTO ad RPO Targets? Eve if a sigle tool ca cover everythig i your SharePoit eviromet that you eed it to, if it ca t do so quickly eough, it is ot goig to be the right tool for the job. Although the two metrics are ot ecessarily related, the performace of your backup ad recovery tool could be just as importat to you as the performace of your overall SharePoit eviromet. If your disaster recovery solutio takes too log to back up or restore some or all of your SharePoit eviromet, you are ot goig to be able to meet the RTO ad RPO targets you have established i your disaster recovery pla. Because we re talkig about both RTO ad RPO targets, you eed to cosider how well the tool completes restore operatios just as much as you do backup operatios. You eed to cosider three factors whe evaluatig a tool s ability to meet your RPO widow targets: the tool s performace capabilities, the size of the compoets you are backig up with it, ad the actual period defied for your RPO target. The iterestig thig about these factors is that it s the combiatio of them that really defies a tool s ability to make or miss your RPO target. If you have a large eviromet ad a tight RPO widow, it s goig to be much more difficult for a tool to back up everythig i a timely fashio. For example, if you have a six-hour RPO target but a tool requires 12 hours to back up your farm, you are guarateed to miss your target. I this istace, you must either chage the RPO target or choose a differet tool or strategy. I the case of restores, it all comes dow to oe thig: ca you restore the targeted fuctioality ad cotet to your SharePoit eviromet i time to meet your RTO target? If a tool ad ay associated recovery process ca t restore SharePoit i time to meet the requiremets your users have established for the eviromet, the tool selected is t the right oe for the job. This is a great reaso to exercise your disaster recovery solutio frequetly over the lifetime of your eviromet, because as it chages ad grows, your tools may ot be able to grow with it. It is far better to fid this out i a test whe it does t cout tha i your productio eviromet whe it really does. Usability Always thik about the usability of a tool whe decidig whether to make it a key part of your disaster recovery solutio. You eed to look for some specific thigs whe evaluatig optios for your disaster recovery solutio. Some are pretty straightforward, ad others are a little less obvious. What a backup or restore tool ca do meas little if you ca t figure out how to use it or if you caot cosistetly use it correctly every time. At the same time, the easier a tool is to use, the larger the pool of people o your team who ca quickly lear how to use it effectively whe called upo with little or o otice. You eed to keep i mid that the resources usig the tool i a time of eed may be those who are available istead of those who kow it best, so how well they ca use the tool may make the differece betwee a successful recovery ad a icomplete or failed oe.

64 Chapter 4 SharePoit Disaster Recovery Best Practices 47 Stability The stability of a tool is its ability to cosistetly deliver the same result time after time. This is somethig that is paramout i creatig a effective disaster recovery solutio. If the tool or tools that you choose are ot able to provide cosistet stability ad predictable usage experiece, the level of risk to your eviromet is goig to grow over time as the likelihood of a error icreases. Ca your tool create a viable backup time after time without errors or icosistecies? If backup files are compressed, ca they be ucompressed every time without loss of data? Are those files always upacked ad restored successfully with every aspect of the eviromet retured to its origial state without chage? You eed to kow that your tool ca reliably do the job you eed it to time after time after time. No Oe Size Fits All The depth ad breadth of your SharePoit eviromet plays a big role i helpig you determie which tool or tools fit best i your disaster recovery solutio. The more movig pieces your farm icludes, whether it be servers, customizatios, or Web sites, the more complex your disaster recovery solutio is likely to be to ecompass it all. It s goig to take a great deal more effort to preserve a farm with four Web frot-ed (WFE) servers, several dedicated Service Applicatio servers, ad clustered SQL Server istaces tha it will a sigle server hostig all roles ad services for the farm. Keep this i mid as you evaluate tools for your disaster recovery solutio, as well as whe your eviromet begis to evolve ad expad its scope, so you ca properly uderstad how those chages impact your solutio s ability to protect SharePoit. The amout of cotet i your SharePoit eviromet also affects the tools you ca ad ca t use to protect it. I a large eviromet, a good SharePoit backup or restore tool eeds to be capable of hadlig large amouts of cotet just as effectively, cosistetly, ad quickly as it does a smaller oe. Some tools state up frot what they do ad do ot support whe it comes to large eviromets; pay close attetio to whatever limitatios ad usage guidelies maufacturers place o each tool. You ve already see how you eed to take this ito accout for the out-of-the-box SharePoit backup ad restore tools, but it s somethig you eed to watch regardless of the tool you decide to use. Coclusio May techical questios ca be aswered with two simple words: It depeds. Although this ca be frustratig to hear, especially if the aswer is delivered sarcastically or flippatly, this respose is ot give to put someoe off or hedge oe s bets. These words are spoke because they re true, ad there are usually umerous factors that go ito a proper aswer for complex techical questios. Aswerig the complex techical questios tied to SharePoit disaster recovery are o differet. Fidig the right solutio ad comig up with a aswer other tha it depeds is ot goig to be somethig as simple as checkig a few boxes i a list ad gettig your perfect match. You eed to really cosider the factors covered i this chapter,

65 48 SharePoit 2010 Disaster Recovery Guide as well as uderstad the stregths ad weakesses of the tools you re cosiderig, so that you ca move from it depeds to here s how we re goig to do it. Oe of the goals i writig this book for SharePoit 2010 was to help you better make that move by addig more iformatio o the proper use cases for the various SharePoit backup ad restore tools discussed. As you read the comig chapters, start thikig about how you re goig to put each approach or tool to use to best protect your SharePoit eviromet or a desigated aspect of it. Whether that is by makig its Web servers highly available, backig up your SQL Server 2008 databases, or backig up SharePoit itself, how you re goig to use the iformatio provided is goig to be critical. To make that practical applicatio easier, read Chapter 13, SharePoit Disaster Recovery Case Studies ad Sample Scearios. It explais some of the use cases available for each solutio or tool ad whe oe might make more sese for you over aother. The advatage we have i helpig you aswer the questio of how do I create the right disaster recovery solutio for my SharePoit eviromet is that by coverig so much of the groud out there o the subject, we ca itroduce you to a rage of optios ad solutios. As you read the followig chapters, pay special attetio to the usage scearios discussed, ad try to see if they do or do t pertai to your specific set of circumstaces. Cosiderig each tool ad techology we describe withi the cotext of your eviromet puts you i the right positio to aswer that critical questio with here s how we re goig to do it istead of it depeds. Now that we ve started to bridge the gap betwee geeral disaster recovery cocepts ad developig your SharePoit disaster recovery pla, you should be able to aswer the followig questios about a pla s capabilities. You ca fid the aswers to these questios i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at com/dowloads. 1. How do recovery targets factor i the scope of your SharePoit disaster recovery solutio? 2. Is it possible to protect every aspect ad compoet of your SharePoit eviromet from damage or loss i the same maer or with a sigle tool? 3. What are some of the ways that the amout of cotet stored i your SharePoit eviromet ca impact the tools i your SharePoit disaster recovery solutio? 4. What are some examples of how chages to your SharePoit eviromet ca affect your disaster recovery solutio? 5. How is the graularity of coverage that a tool provides goig to ifluece your decisio o whether to iclude it i your disaster recovery toolbox?

66 5 Widows Server 2008 Backup ad Restore I This Chapter Backup Targets Before You Begi Backig Up Widows Server 2008 Restorig Widows Server 2008 As discussed i Chapter 4, SharePoit Disaster Recovery Best Practices, SharePoit is a complex applicatio platform that depeds o differet services ad systems for proper operatio. You ca evisio these services ad systems as layers i a software stack much like a layer cake. The layers sit atop oe aother, ad each layer i the stack depeds o the oes beeath it. SharePoit sits at the top, fully depedet o all the layers beeath it. If SharePoit is the top layer i the stack, the bottommost foudatioal layer of software is the Widows Server operatig system (OS). Whe ew hardware is provisioed for use with SharePoit or ay Microsoft applicatio platform the Widows Server OS is almost always the first prerequisite istallatio. Without Widows Server ad its platform services, SharePoit would ot have a way of iteractig with the server hardware, etwork, ad other physical devices. Productio istallatios of SharePoit require a uderlyig OS that is 64 bit ad some versio of Widows Server Valid versios iclude these: Widows Server 2008 R2 (Web, Stadard, Eterprise, ad Dataceter editios) Widows Server 2008 with Service Pack 2 (SP2) (Web, Stadard, Eterprise, ad Dataceter editios) Widows Small Busiess Server 2008 with SP2 Widows Essetial Busiess Server 2008 with SP2 49

67 50 SharePoit 2010 Disaster Recovery Guide SharePoit 2010 is ot supported o ay Widows Server 2008 Server Core istallatios, because those istallatios do ot cotai some of the compoets eeded to cofigure ad ru SharePoit. Note: Although Microsoft supports the istallatio of SharePoit Server 2010 ad Share- Poit Foudatio 2010 o 64-bit versios of Widows 7 ad Widows Vista Service Pack 1 (SP1) or greater, such istallatios are iteded for developmet use oly. The importat foudatioal role that Widows Server 2008 plays with SharePoit demads that the OS ad the way it works with SharePoit data be uderstood for proper disaster recovery plaig. This chapter examies how SharePoit uses the Widows Server 2008 OS, where SharePoit ad the OS store relevat cofiguratio data, ad areas you should cosider targetig durig backup. It also details available backup optios, as well as factors to cosider while plaig a backup strategy. Fially, this chapter presets a walk-through of commo backup ad restore operatios for the OS. The visual examples provided i this chapter were geerated i a testig eviromet usig the followig platforms ad compoets. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 Stadard Editio with SP1 (build ) Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 SharePoit. SharePoit Server 2010 Trial (Beta) with Eterprise Cliet Access Licese (build 4536) Backup Targets To discuss backup ad restore i a meaigful fashio, you must first uderstad the data that you ited to capture ad safeguard. As a complex applicatio platform, SharePoit stores busiess ad cofiguratio data i a variety of locatios. It should be o surprise that a sigificat amout of it goes ito SQL Server; after all, the first database that is created whe a ew Share- Poit farm is provisioed is the farm cofiguratio database. Note: SQL Server ad its fit ito the SharePoit disaster recovery picture are discussed i depth i Chapter 7, SQL Server 2008 Backup ad Restore. Although SharePoit relies o SQL Server for the storage of data, the services of Widows Server cotribute i a equally sigificat maer to the operatio ad delivery of fuctioality withi

68 Chapter 5 Widows Server 2008 Backup ad Restore 51 the overall SharePoit farm. Without Iteret Iformatio Services (IIS), for istace, Share- Poit would ot be able to serve Web pages i respose to cliet requests. Without the Widows Registry, SharePoit could ot persist ad retrieve cofiguratio iformatio that govers farm membership, database coectivity, ad more. As you might expect, each of these costituet services processes data, maages cofiguratio iformatio, ad represets oe or more targets from a backup ad restore perspective. This sectio examies Widows server as a platform, a subset of its services that are relevat to SharePoit, ad aspects of both that are importat withi the larger SharePoit disaster recovery cotext. Customizatios A SharePoit customizatio cosists of some combiatio of files ad cofiguratio elemets deliverig fuctioality that ehaces or i some way alters the out-of-the-box SharePoit experiece. Customizatios ca add ew user iterface (UI) elemets ad behavior for users of Share- Poit, chage the way that SharePoit iteracts with other systems, ad much more. Uderstadig customizatios is importat withi the cotext of Widows server backup ad restore because may of the file ad cofiguratio elemets that costitute a customizatio reside i the file system of the Widows server ot withi a SQL Server database. For example: Web Parts XML cofiguratio files, such as Feature or site defiitio XML files List defiitios, custom colums, ad ew cotet types Maaged assemblies ad other code libraries Resource (.resx) files The mechaism by which the files associated with a customizatio are backed up ad restored is determied largely by how the customizatio elemets make it ito the file system of the server. For purposes of backup targetig, customizatios are classified i oe of two ways: Cetrally maaged customizatios. A customizatio is cetrally maaged whe all its files ad assets are aggregated ito a SharePoit solutio package ad deployed via SharePoit s solutio deploymet ifrastructure. A solutio package is a special cabiet (.cab) archive file with a.wsp extesio, ad the file ad its cotets coform to a structure that SharePoit uderstads. Solutio packages, also kow as WSPs, are added to a SharePoit farm s solutio store, ad admiistrators deploy or retract their cotets through Cetral Admiistratio or PowerShell. SharePoit is fully aware of the chages that a solutio package makes; it ca reapply ad retract those chages as eeded. Decetralized customizatios. If a customizatio is deployed through a mechaism that does ot ivolve the farm solutio store, that customizatio is said to be decetralized. This

69 52 SharePoit 2010 Disaster Recovery Guide icludes the maual copyig of files to each of the servers withi the farm ad the chagig of web.cofig files by had. It ca also iclude usig a third-party istaller techology that is t explicitly desiged to itegrate with SharePoit. Whe customizatios are decetralized, there is always the potetial for SharePoit to overwrite files ad modificatios that are made for or by the customizatio because SharePoit simply is t aware of them. You should isist upo the use of cetrally maaged customizatios withi your farm wheever possible. SharePoit solutio packages are widely accepted as a best practice for the deploymet of files, resources, ad other customizatio items to the SharePoit farm. I additio, solutio packages greatly reduce the maual work required for the backup ad recovery of customizatios. Whe a solutio package is added to a SharePoit farm via the Add-SPSolutio Power- Shell cmdlet, for example, the cotets of the package are copied to the farm s solutio store withi the cofiguratio database. You ca capture such solutios through both SharePoit ad SQL Server backup mechaisms. Solutios that are preset i the farm solutio store are also viable targets for cofiguratio-oly backup ad restore. The backup ad restore picture for decetralized customizatios is sigificatly less attractive. Although you ca geerally automate the backup of the associated files, restoratio of the items captured by those backups is more challegig. New files that are added to the file system for a customizatio ca geerally be restored i-place directly from a backup, but chages to shared cofiguratio files such as a web.cofig caot be directly restored because such a restoratio could overwrite existig cofiguratio elemets eeded by other features ad solutios. I such circumstaces, maual applicatio of chages to affected files is the safest approach, albeit a tedious oe. Decetralized customizatios uderscore the eed for thorough chage maagemet procedures ad associated documetatio, as described i Chapter 4. The costituet files that are deployed through a customizatio ed up i three possible areas withi the server file system. SharePoit Root Whe istalled i Widows Server 2008, most applicatios create a directory for use withi the Program Files directory. (This directory is the locatio poited at by the %PROGRAMFILES%PATH variable i the server s system drive [typically the C: drive].) See Figure 5.1 for a example. This directory usually cotais the executables, libraries, ad cofiguratio files ecessary for the applicatio to ru o the server. SharePoit follows this covetio, but oly to a poit. After you istall SharePoit, you should see a directory amed Microsoft Office Servers withi the Program Files directory. A examiatio of its cotets reveals several files ecessary to ru SharePoit. Geerally speakig, the cotets of the Microsoft Office Servers directory are relatively uchagig. Where SharePoit strays from the covetioal approach to the Program Files directory is i its use of a directory kow as the SharePoit Root.

70 Chapter 5 Widows Server 2008 Backup ad Restore 53 Figure The Program Files directory i a Widows Server 2008 istallatio hostig SharePoit The SharePoit Root is also located withi the Program Files directory, but it is ested withi several other folders that other Microsoft applicatios sometimes leverage. As show i Figure 5.2, the SharePoit Root resides at %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extesios\14\ withi the server file system. Note: The SharePoit Root has ot always bee widely kow as such. I Widows SharePoit Services (WSS) v3 ad Microsoft Office SharePoit Server (MOSS) 2007, the directory was labeled as 12 rather tha 14 ad was commoly referred to as the 12 Hive. Prior to that, with WSSv2 ad SharePoit Portal Server (SPS) 2003, the folder was labeled as 60 ad oftetimes referred to as the 6 Hive or 60 Hive. So what is i the SharePoit Root? The short aswer is Quite a bit. By default, the directory cotais a umber of applicatios, libraries, ad resources that are crucial to SharePoit s operatio:.net assemblies that house the compiled code that is the SharePoit platform, a variety of differet diagostic logs, out-of-the-box image files, ASP.NET applicatio ad admiistrative pages, ad SharePoit Features to ame just a few. I additio to its role as the cetral hub for may out-of-the-box SharePoit files, the SharePoit Root plays a importat role for customizatios. Whe farm-wide assets such as admiistrative

71 54 SharePoit 2010 Disaster Recovery Guide Figure 5.2 The SharePoit Root directory i a Widows Server 2008 istallatio. pages, site templates, ad shared images are packaged ito a customizatio, they are ormally deployed to oe or more folders withi the SharePoit Root. For cetrally maaged customizatios, PowerShell or Cetral Admiistratio hadles the additio of ew files ad chages to the SharePoit Root automatically durig solutio package deploymet. You ca easily check the istallatio ad deploymet status of cetrally maaged customizatios withi the farm withi Cetral Admiistratio usig the Solutio Maagemet page show i Figure 5.3. If a cetrally maaged solutio package is later retracted, SharePoit takes care of removig the files ad chages it made earlier. No maual itervetio is required o the part of the admiistrator. The SharePoit Root is just as importat to decetralized customizatios, but admiistrators must maually carry out file copies, file removals, ad cofiguratio chages withi the Share- Poit Root. SharePoit is t aware of the chages beig made i this fashio, ad there is always a risk that additios ad chages that are made by other admiistrators or SharePoit itself, for that matter could coflict with oe aother. If decetralized customizatios are used withi your farm, the SharePoit Root is a madatory backup target. Without a copy of the SharePoit Root, you risk losig part or all of the files that comprise your customizatios. I the case of cetrally maaged customizatios that are deployed usig SharePoit solutio packages, though, a backup of the SharePoit Root is secodary. Backig up the SharePoit Root is still recommeded for the sake of redudacy, but the primary poit of capture, maagemet, ad deploymet for solutio packages is the solutio store withi the SharePoit farm cofiguratio database.

72 Chapter 5 Widows Server 2008 Backup ad Restore 55 Figure 5.3 The Solutio Maagemet page withi Cetral Admiistratio. Ietpub The Web Server (IIS) server role is a required role o ay Widows server that rus SharePoit. Whe this role is eabled o a server, a Ietpub folder is created to house much of the file ad cofiguratio data that IIS uses to serve up Web sites ad carry out associated operatios. By default, the Ietpub folder is located at C:\ietpub withi the server file system, as show i Figure 5.4. The actual locatio of the folder may vary, though, depedig o how IIS has bee cofigured. Each of the Web applicatios withi a SharePoit farm possesses oe or more folders withi the Ietpub directory of each farm member, where the Microsoft SharePoit Foudatio Web Applicatio service is ruig. To be more specific, a Web applicatio has oe Web site folder for its Default zoe mappig. For each zoe beyod the Default zoe that the Web applicatio has bee exteded to, a additioal Web site ad associated folder exists withi Ietpub. For example, a Web applicatio that has bee exteded to the Iteret ad Extraet zoes possesses three folders withi Ietpub oe folder for the Default zoe, oe folder for the Iteret zoe, ad oe folder for the Extraet zoe. The root folder for each of the Web sites that map to a SharePoit Web applicatio is located withi the Ietpub\wwwroot\wss\VirtualDirectories directory by default. Each of the

73 56 SharePoit 2010 Disaster Recovery Guide Figure 5.4 The Ietpub folder i its default locatio. folders is amed accordig to the host header that is applied to the zoe of its correspodig Web applicatio withi SharePoit. If o host header is i use, the listeer port of the associated Web applicatio is employed istead. Of course, you ca specify a odefault path for the folder that is actually used whe you create the SharePoit Web applicatio. Chagig the cotets of the Path text box i the IIS Web Site sectio of the Create New Web Applicatio dialog box istructs SharePoit to use your desired path as the Root folder for the Web applicatio rather tha the default. Note: The oe exceptio to the amig covetio described is the Cetral Admiistratio Web applicatio s Default zoe Web site. Regardless of the port assiged to the Cetral Admiistratio site collectio durig provisioig, the folder ame applied correspods to a radom high port that SharePoit selects. Figure 5.5 illustrates the cotets of a SharePoit Web applicatio that is mapped to the default Web site o the server. Customizatios cotribute to ad affect the cotets of the SharePoit Web applicatio Ietpub folders i a hadful of ways. First ad foremost, each of the folders has a web.cofig file that govers may of the cofiguratio ad operatioal aspects of its associated Web applicatio. Customizatios that are scoped at the Web applicatio, site collectio, or Web level usually

74 Chapter 5 Widows Server 2008 Backup ad Restore 57 Figure 5.5 The cotets of a IIS Web site folder that maps to a SharePoit Web applicatio. require modificatios to a Web site s web.cofig file for proper operatio. These cofiguratio chages ca permit the executio of code preset i o-sharepoit.net assemblies, add ew applicatio settigs, wire up ew HttpModule ad HttpHadler etries, ad more. Chages to the web.cofig files of a Web site occur most frequetly, but they are ot the oly chages that a customizatio may make or require withi the Ietpub directory ad its subdirectories. Other examples iclude these: The additio of.net assemblies to the bi subdirectory Navigatio chages to the sitemap file(s) withi a _app_bi subdirectory Web Part defiitio ad resource file additios to various subdirectories The guidelies for backup ad recovery of the Ietpub folder are much the same as those for the SharePoit Root folder. Cetrally maaged customizatios ormally affect required chages o the Ietpub folder whe they are deployed through SharePoit Cetral Admiistratio or PowerShell. Whe they are retracted, those chages that solutio packages have made are also retracted. Backup of the Ietpub folder is a good practice, but it is redudat whe cosidered alogside solutio packages that properly deploy ad retract their ow Ietpub files ad settigs. Decetralized customizatios require that the Ietpub folder ad all its cotets be backed up. Failure to do so results i the loss of all files ad chages that have bee made i the evet of a

75 58 SharePoit 2010 Disaster Recovery Guide disaster or failure of the server. I additio, recovery i a disaster sceario is a tricky propositio. As metioed, may customizatios modify the cotets of the Web site folders used by each of SharePoit s Web applicatios. This is especially true for the web.cofig file used by each SharePoit Web site withi IIS. Durig recovery operatios that ivolve decetralized customizatios, it is a admiistrator s resposibility to esure that all ecessary chages to web. cofig files (ad the rest of the Ietpub area) are properly applied ad ocoflictig. Global Assembly Cache Every Widows operatig system with oe or more istalled versios of the Microsoft.NET Framework possesses a Global Assembly Cache, or GAC. The GAC is a protected operatig system locatio where.net assemblies are located ad shared for use by multiple applicatios. Withi the Widows Server operatig system, you ca fid the GAC at %WINDIR%\Assembly, as show i Figure 5.6. Figure 5.6 The GAC..NET assemblies that are placed withi the GAC behave differetly from those that are located elsewhere withi the file system of the server, icludig those that are placed withi the bi folder of a Web site withi the Ietpub area. Here are some importat differeces: Assemblies withi the GAC are fully trusted. The GAC supports the istallatio of multiple versios of the same assembly. The.NET assembly resolver checks the GAC before lookig elsewhere, such as i a bi folder.

76 Chapter 5 Widows Server 2008 Backup ad Restore 59 Beig a.net applicatio platform itself, SharePoit makes extesive use of the GAC. May of the assemblies that SharePoit uses are withi the GAC. By extesio, may customizatios choose to place assemblies i the GAC. I some cases, such as customizatios that iclude feature receivers, placemet of assemblies withi the GAC is madatory. As with the SharePoit Root ad Ietpub folders, cetrally maaged customizatios hadle the placemet ad retractio of assemblies withi the GAC directly through the SharePoit solutio deploymet framework. Backup of the GAC is a recommeded actio for cetrally maaged customizatios, but oly as a step that is redudat with SharePoit farm or SQL Server backups. I the case of decetralized customizatios, placemet of assemblies withi the GAC is a maual affair or, at the very least, oe that SharePoit does t cotrol. As a result, the GAC must be targeted for backup operatios to esure that the assemblies supplyig rutime fuctioality for such customizatios are captured ad preserved i the evet of a disaster. IIS IIS receives requests for SharePoit pages ad hads redered pages back to cliet browsers ad applicatios. This descriptio is a gross oversimplificatio of the role that IIS plays, but it serves as a good startig poit to uderstadig the ways i which IIS serves ad iteracts with Share- Poit. Iteractio with IIS is commoly carried out through its maagemet applicatio, as show i Figure 5.7. Figure 5.7 IIS Maager.

77 60 SharePoit 2010 Disaster Recovery Guide As a Web server, IIS faithfully carries out may duties o behalf of SharePoit too may to fully describe here. Some of the more well-kow oes, though, iclude the followig: Maagig oe or more istaces of the SharePoit applicatio process Hostig Service Applicatios ad the commuicatios betwee them Eforcig security at the trasport layer Providig static ad dyamic compressio for outgoig data IIS is eabled through the Web Service (IIS) role withi Widows server, ad mechaisms withi SharePoit afford a great deal of cotrol over IIS ad how it operates, both directly ad idirectly. It is ot possible to maage all facets of IIS from withi SharePoit or PowerShell, though. A umber of settigs ad cofiguratio items tied to IIS must be addressed ad targeted separate from SharePoit for disaster recovery purposes. Cofiguratio As a complex set of services i its ow right, IIS depeds o a sigificat amout of cofiguratio data to gover its ow operatios. I IIS6 uder Widows Server 2003, this cofiguratio data was maitaied i a database kow as the IIS Metabase. With Widows Server 2008 ad IIS7, the Metabase has bee replaced by a set of XML cofiguratio files that are located i the %WINDIR%\System32\Ietsrv\Cofig folder. The followig three files primarily gover IIS operatios: The ApplicatioHost.cofig file houses cofiguratio data for each of the Web sites ad applicatios that IIS maages ad serves. The cotets of this file are updated each time a cofiguratio chage is made withi IIS. The Admiistratio.cofig file cotais settigs that relate to the maagemet of IIS itself, icludig data that govers maagemet modules for the IIS Maager applicatio. I most cases, the cotets of this file are static. The Redirectio.cofig file is employed whe IIS is beig ru i shared cofiguratio mode. Because the shared cofiguratio feature of IIS is ot supported with SharePoit, this cofiguratio file is of little practical use o SharePoit servers. Regular backups of the cofiguratio folder ad subfolders are a best practice, because they afford you the opportuity to roll back ay IIS chages that may adversely affect the operatio of Web sites, Web services, ad SharePoit Service Applicatios. You ca back up the cofiguratio folder ad subfolders directly, or you ca make a more targeted backup directly usig the AppCmd.exe tool that is described later i this chapter. Eve if you do t make regular backups, IIS itself affords a certai degree of resiliecy through its cofiguratio history feature. As chages are made to IIS, the cotets of the ApplicatioHost.

78 Chapter 5 Widows Server 2008 Backup ad Restore 61 cofig file chage. By default, IIS checks for chages to the ApplicatioHost.cofig file every two miutes. If a ew versio of the file is foud to be i effect, IIS takes a sapshot of the file ad places it i the %SYSTEMDRIVE%\ietpub\history folder. IIS keeps up to 10 historical versios of the ApplicatioHost.cofig file i this way. Tip: You ca alter or eve tur off the operatio of the cofiguratio history feature by editig the system.applicatiohost/cofighistory <sectioschema4 elemet withi the iis_schema.xml file located withi the %WINDIR%\system32\ietsrv \cofig\ schema\ folder. Although the cofiguratio history feature does t protect IIS agaist catastrophic server failure, it does support the rollback to a previous IIS cofiguratio if problems are ecoutered followig chages to IIS. Secure Socket Layer Certificates IIS uses Secure Socket Layer (SSL) certificates to establish secure chaels of commuicatio betwee cliets ad the Web server. I the cotext of SharePoit, cliets refers ot oly to ed user Web browsers, but to Service Applicatios commuicatig i a itra- ad iter-farm capacity. Cliets also iclude ay other requestors directig HTTPS traffic to the SharePoit server(s). A SSL certificate supports secure Web server commuicatios i two importat ways. First, the SSL certificate provides the evidece a cliet requires to validate that the server respodig to the cliet s Web requests has the authority to do so. Oce this validatio has occurred, the SSL certificate allows the Web server ad cliet to establish a shared key that ca symmetrically ecrypt commuicatios betwee the cliet ad the Web server. Although IIS uses SSL certificates directly, the certificates are either stored withi Web sites or captured whe a IIS cofiguratio backup is performed. SSL certificates that IIS uses are stored withi the server s local machie certificate store ad maaged through the Certificates Microsoft Maagemet Cosole (MMC) sap-i, as show i Figure 5.8. You should back up the cotets of the certificate store aytime you chage it through the additio, update, or removal of certificates. I the evet of a disaster, restorig the cofiguratio of IIS without the associated certificates it might eed ca adversely impact secure commuicatios with cliets. As metioed earlier, this ca iclude iteractios betwee cliet browsers ad the Web server as well as secure commuicatios betwee SharePoit farm Service Applicatios. Widows Registry The Widows Registry is a repository that stores cofiguratio data for the Widows Server 2008 operatig system, its hardware, ad much of the software istalled o it. Although the

79 62 SharePoit 2010 Disaster Recovery Guide Figure 5.8 The Certificates MMC sap-i. role of the Registry is ot as all ecompassig as it was prior to the advet of XML ad the may cofiguratio files that leverage it, you ca still thik of the Registry as the cofiguratio database for Widows. A SharePoit farm stores much of its cofiguratio data withi the farm cofiguratio database, but may of the services ad compoets that costitute the SharePoit platform use the Registry for settigs ad cofiguratio storage. The SharePoit Timer service ad some of its Registry-residet settigs appear i Figure 5.9. Figure 5.9 SharePoit Timer Service Registry settigs.

80 Chapter 5 Widows Server 2008 Backup ad Restore 63 I additio to SharePoit s services ad compoets, may applicatios associated with SharePoit store settigs ad other cofiguratio data withi the Registry. Ay Widows server backup strategy that you employ must accout for the Registry ad capture its cotets. Providers ad Additioal Depedecies This fial category of backup target is the catchall for ay services, compoets, applicatios, ad other software that is ot covered withi the SharePoit platform itself but must be addressed at the Widows server level for purposes of disaster recovery. Followig are some examples of items i this category: Decetralized customizatios that require the placemet of files, settigs, or other data outside of the SharePoit Root, GAC, or Ietpub areas Drivers, cliets, ad coectio iformatio for database techologies other tha SQL Server upo which some aspect of SharePoit operatios deped Nostadard autheticatio providers that SharePoit Web applicatios leverage Custom IFilter ad Protocol Hadler additios to exted SharePoit search fuctioality You must formulate a backup ad restore strategy for each of these items, ad other items withi this category, o a case-by-case basis. Before You Begi Now that you possess a uderstadig of those items withi the server operatig system that you should back up as part of a disaster recovery pla, it is importat to pause ad cosider how to address the backup targets this chapter has discussed. What are the tools you have at your disposal? What approach should you take? Are there ay questios you should be askig yourself before divig headlog ito the backup process? At a miimum, it is importat to simply recogize the eed for backig up your Widows Server 2008 servers; if you do t curretly have a backup pla, you should seriously cosider implemetig oe for your etire orgaizatio s servers, ot just your SharePoit resources. Without server backups of some sort, a disaster recovery pla must iclude provisios for the rebuildig ad cofiguratio of Widows servers. Such rebuilds are commoly a time-cosumig procedure oe that ca quickly limit your ability to meet aggressive recovery poit objective (RPO) ad recovery time objective (RTO) requiremets. The pages that follow outlie how to prepare for ad create a server backup usig some of the tools icluded with Widows Server 2008, as well as how to idividually back up some of the compoets previously metioed that SharePoit depeds o for key fuctioality.

81 64 SharePoit 2010 Disaster Recovery Guide Selectig a Backup Approach After you decide to coduct backups, the ext most logical questio is, Which approach is right for me? A poit this book states repeatedly is that there is o oe-size-fits-all approach to disaster recovery; that otio holds true for the subtopics of server backup ad restore as well. Istead of tryig to exhaustively describe every possible optio for data protectio ad recovery available o the Widows Server platform, this chapter discusses two geeral approaches to data protectio. Each has its stregths, weakesses, ad associated toolsets, ad both play a importat role i ay comprehesive strategy that may be assembled to address your specific disaster recovery eeds. Full Server Backup A full server backup is a complete backup that captures the etire cotets of the server, icludig the operatig system, istalled applicatios, server cofiguratio, ad ay data housed o the server. If ay software compoet of the server is corrupt, damaged, or deleted, you ca typically restore or recover it i some way usig the full backup. The true stregth of the full server backup is ot its compoet-level restore ability, though, but rather its support for full recovery of the server i catastrophic disaster scearios. I the evet of a complete server failure through the loss of its hard drives, for example, the full backup ca restore the server s operatig system, cofiguratio, applicatios, ad other data o ew hard drives. Eve if you lose the etire server, hardware ad all, you ca restore a full backup oto idetical hardware to essetially brig the server back olie. Although this type of bare-metal backup ad recovery was techically possible prior to Widows Server 2008 usig the built-i Widows NTBackup ad its Automated System Recovery optio, it was ot for the fait of heart. Backup ad restore was overhauled ad streamlied with the Widows Server Backup fuctioality i Widows Server 2008, however, ad it is ow much easier to perform backups, establish a backup schedule, ad carry out recoveries whe eeded. Multiple aveues of access to the server backup fuctios exist, icludig a MMC sap-i (used idividually or through Widows Server 2008 s Server Maager), the wbadmi commad lie tool, ad umerous PowerShell cmdlets. The ew Widows Server Backup icludes a sigificat umber of backup-related ehacemets, but they are ot the etire story. Ehacemets i backup coverage are matched o the recovery side of the equatio by the Widows Recovery Eviromet (Widows RE). If Widows Server 2008 becomes corrupt or caot be started for some reaso, the stad-aloe Widows RE ca be started to coduct a recovery. Based o the Widows Preistallatio Eviromet, Widows RE possesses its ow graphical user iterface (GUI) ad comes with a set of recovery-orieted tools that greatly speed ad simplify the process of system recovery. You ca eve coduct bare-metal recoveries with the aid of the Widows RE restore wizard.

82 Chapter 5 Widows Server 2008 Backup ad Restore 65 Idividual Compoet Backup The stregth of Widows Server Backup is its support for full server protectio ad recovery i true disaster scearios, ad this makes it the logical choice for disaster recovery scearios where etire servers must be protected. I situatios where it is desirable to protect specific subsystems ad compoets withi the overall operatig system agaist user-iduced outages, admiistrative miscofiguratio, ad other related problems, oe or more specific protectio strategies may be appropriate for idividual compoets ad backup targets. The good ews is that Widows Server 2008 icludes a umber of differet tools to address each of the backup targets that have bee discussed thus far: AppCmd.exe for IIS cofiguratio IetMgr.exe ad the Certificates MMC sap-i for SSL certificates Widows Server Backup for the GAC ad other file system targets RegEdit.exe for the Widows Registry The stregth of a compoet-based backup approach is that it is typically arrower i scope ad easier to use withi a idividual backup target. If you eed to roll back a server s IIS cofiguratio to a previous state, for istace, it is quicker, easier, ad less ivasive to use the AppCmd.exe utility tha to execute a full server recovery. Of course, arrow backup approaches such as these come with a umber of limitatios. Oe dowside to backig up idividual compoets is the lack of cohesio betwee the tools that are used. Some are drive from the commad lie, others have a GUI, ad o two are alike. I additio, the tools themselves are part of the operatig system ad caot be employed uless the server is operatioal. These limitatios mea that per-compoet backups aloe should geerally be cosidered as a additio to full server backups, ot as a replacemet for them. Other Optios I additio to tools that play a direct role i Widows Server backup ad restore, Widows has additioal features ad fuctios that you ca leverage to provide some measure of protectio agaist outages, corruptio, ad other service disruptios. For example, the Shadow Copies of Shared Folders optio gives you the capability to recover accidetally deleted or overwritte files withi file shares. This feature, ad others like it, are ot strictly for disaster recovery use but ca be employed as part of disaster recovery strategy i certai limited scearios. You are ecouraged to explore the Widows Server platform to lear about this feature ad others like it to see if it may be useful to you i your overall disaster recovery strategy. Although the focus of this chapter is o tools that are icluded with Widows Server 2008, they are by o meas the oly optios you have available to you. May third-party tools exted ative OS fuctioality or preset disaster recovery optios that go well beyod those that are available out of

83 66 SharePoit 2010 Disaster Recovery Guide the box. If you re iterested i reviewig third-party backup ad restore tools for Widows Server 2008 ad SharePoit i geeral, be sure to look at Appedix B, Third-Party Tools, foud o the Cegage Learig Web site at Backup Prerequisites Prior to attemptig ay form of full server or compoet-specific backup, you eed to address a few prerequisites. Eablig the Widows Server Backup Features Although Widows Server Backup is icluded with Widows Server 2008, it is ot eabled by default. Attempts to lauch the Widows Server Backup applicatio from the Admiistrative Tools meu or WbAdmi.exe from the commad lie yield the widow see i Figure Figure 5.10 Widows Server Backup Feature ot eabled. Eablig Widows Server Backup o the server is a straightforward process: 1. Esure that you are logged oto the server as a admiistrator capable of makig server feature chages. 2. Click the Start butto, ad avigate to Admiistrative Tools, Server Maager, as show i Figure After the appropriate sap-i has bee added ad the Server Maager has eumerated each of the roles that are active o the server, you are preseted with a Roles Summary scree. I the left-had tree view, select the Features ode uder the Server Maager root. Doig so displays a summary of active features o the server, as show i Figure 5.12.

84 Chapter 5 Widows Server 2008 Backup ad Restore 67 Figure 5.11 Lauchig the Server Maager. 4. Select the Add Features lik alog the right side of the Features Summary. Doig so displays the Add Features Wizard. Withi the list of available features, scroll dow ad locate the expadable ode labeled Widows Server Backup Features. Expad the ode ad place check boxes ext to both the Widows Server Backup ad Commad Lie Tools optios, as show i Figure 5.13, ad the click the Next butto. Note: The Widows Server Backup optio actually istalls the MMC sap-i, services, ad the WbAdmi.exe commad lie tool. The Commad Lie Tools optio, o the other had, simply eables the creatio ad maagemet of backups usig PowerShell. The Commad Lie Tools optio is strictly optioal but depeds o the istallatio of the Widows Server Backup optio.

85 68 SharePoit 2010 Disaster Recovery Guide Figure 5.12 Features Summary withi Server Maager. 5. A cofirmatio dialog appears, as show i Figure Click the Istall butto to carry out the feature istallatio. 6. As the istallatio of the feature is carried out, a progress bar keeps you apprised of the status of the istall, as show i Figure Oce the Widows Server Backup Features have bee istalled successfully, as show i Figure 5.16, click the Close butto to fiish the process ad close the Add Features Wizard widow. After the Add Features Wizard widow has closed, you ca also close the Server Maager widow. Oce these steps are complete, the server is capable of carryig out full server backup ad restore operatios usig Widows Server Backup. Path Cosideratios Eablig the Widows Server Backup Features as just described addresses prerequisite cocers for both full server backup/recovery ad targeted file system backup/recovery if you employ idividual compoet backups. For the bulk of the remaiig tools that are used for idividual compoet backup ad restore operatios, prerequisites do ot exist. You ca easily lauch the tools from the Ru dialog box that you ope from the Start meu.

86 Chapter 5 Widows Server 2008 Backup ad Restore 69 Figure 5.13 Selectig the Widows Server Backup Features. The oe tool requirig a bit of preparatory actio is the AppCmd.exe tool that backs up ad restores a server s IIS cofiguratio. AppCmd.exe resides i the %WINDIR%\System32\ietsrv directory, which is ot oe of the default paths icluded withi the server s Path eviromet variable. As a result, attempts to execute AppCmd.exe from aywhere other tha the %WINDIR% \System32\ietsrv folder fail, as show i Figure Note: By default, the %WINDIR% folder traslates to C:\Widows i most server eviromets. Examples ad screeshots that referece the %WINDIR% path for the remaider of this chapter assume this traslatio. There are two ways to address this limitatio. The obvious approach is to esure that attempts to call AppCmd.exe from withi the PowerShell ad commad lie eviromets are doe so with full path iformatio. Although this certaily works, typig C:\Widows\System32\ ietsrv\appcmd.exe every time AppCmd.exe is refereced is laborious to say the least.

87 70 SharePoit 2010 Disaster Recovery Guide Figure 5.14 Cofirmig the istallatio. The more viable log-term approach is to modify the server s Path eviromet variable to iclude the C:\Widows\System32\ietsrv path. You ca easily accomplish this through a few simple steps. 1. Esure that you are logged oto the server as a admiistrator capable of makig server eviromet chages. 2. Ope the Start meu ad avigate to the Cotrol Pael. Oce the Cotrol Pael has opeed, select the System ad Security lik, ad the select the System lik. Doig so opes the server s System widow, as show i Figure Select the Advaced System Settigs lik ear the top left of the System widow. Oce selected, the System Properties tabbed dialog box opes. Esure that the Advaced tab is selected, as show i Figure Click the Eviromet Variables butto ear the lower-right corer of the System Properties dialog box. Oce you ve doe this, the Eviromet Variables dialog box

88 Chapter 5 Widows Server 2008 Backup ad Restore 71 Figure 5.15 Istallatio of the feature. opes. The top portio of the dialog box shows per-user eviromet variables, whereas the lower half of the widow shows eviromet variables that apply system wide. Scroll through the System variables i the lower half of the widow ad locate the Path variable, as show i Figure With the Path variable selected, click the lower Edit butto. Doig so opes the Edit System Variable dialog box. Eter the Variable Value text box, ad scroll as far to the right (that is, the ed of the lie) as possible. Whe you reach the ed of lie, add a trailig semicolo (if oe is ot preset) ad the path C:\Widows\System32\ietsrv\, as show i Figure Click the OK butto o the Edit System Variable dialog box, the Eviromet Variables dialog box, ad the System Properties dialog boxes to accept chages ad close them. With the dialog boxes closed, close the System widow. 7. Cofirm that the Path variable chages have bee accepted ad icorporated ito the eviromet. To do this, ope a PowerShell widow by opeig the Start meu ad

89 72 SharePoit 2010 Disaster Recovery Guide Figure 5.16 Successful istallatio of the Widows Server Backup Features. Figure 5.17 AppCmd.exe called without path qualificatio.

90 Chapter 5 Widows Server 2008 Backup ad Restore 73 Figure 5.18 The server System widow. avigatig to All Programs, Accessories, Widows PowerShell, Widows PowerShell. Whe the PowerShell widow has opeed, type AppCmd.exe ad press Eter. Istead of your seeig the error that appeared previously i Figure 5.17, the AppCmd.exe applicatio executes, ad you are preseted with somethig that appears similar to Figure With the eviromet variable chage i place, you ca call AppCmd.exe iteractively without path iformatio i both commad lie ad PowerShell eviromets. This path support exteds to PowerShell scripts ad commad lie batch files. Choosig a Storage Locatio Where you choose to back up your data is a decisio you should make with the same care ad deliberatio as selectig the data to back up. If you choose to store your backups o the file system of a server you are tryig to protect, for istace, your ability to recover data i the evet of catastrophic server failure may be severely limited uless you take additioal steps to move or copy the backups to a more accessible locatio prior to the disaster.

91 74 SharePoit 2010 Disaster Recovery Guide Figure 5.19 The System Properties tabbed dialog box. Full server backups that utilize Widows Server Backup ca use four differet storage locatios or types. Each has beefits ad disadvatages associated with it: Remote shared folders ca be used as a storage locatio for both scheduled backups ad oe-time backups. The use of a shared folder o aother server is ideal for full server backups give that such backups are commoly used i the evet of catastrophic server failure. If the server that is backed up fails, the backup is uaffected ad available for recovery operatios through the shared folder. The primary limitatio associated with remote shared folders is that such folders ca store oly oe backup per server. If you eed more tha oe backup, or you must maitai a backup history i some form, remote shared folders aloe may ot be suitable. DVD/optical/removable media ca be used as a storage locatio oly for oe-time backups of a server. May types of optical ad other removable media ca also be slower, write-oce i ature, or of limited capacity whe compared to other disk-based media types.

92 Chapter 5 Widows Server 2008 Backup ad Restore 75 Figure 5.20 The Eviromet Variables dialog box. Figure 5.21 The Edit System Variable dialog box. Cosiderig these limitatios, backups made o such media are geerally impractical for disaster recovery scearios. Iteral hard disks ca be used as a storage locatio for both scheduled backups ad oetime backups. Ulike remote shared folders, iteral hard disks ca house multiple backups of the server to which they are attached ideal i scearios where backup history or

93 76 SharePoit 2010 Disaster Recovery Guide Figure 5.22 Successful executio of AppCmd.exe followig Path variable modificatio. versioig is desired. The sigle greatest shortcomig associated with iteral hard disk backups is the fact that they are directly attached to the server that they are protectig. You must make provisios to relocate backup data regularly to prevet it from fallig victim to disaster evets impactig the housig server. Note: May etwork-attached storage (NAS) ad storage area etwork (SAN) optios allow hard disk storage that is exteral to the server to actually preset itself as if it were iteral to the server. Although ormally more expesive tha simple iteral disks, NAS ad SAN optios oftetimes afford additioal beefits such as data replicatio, additioal redudacy, ad versioig. These beefits ca make such optios extremely attractive for disaster recovery ad backup purposes, provided your budget ca accommodate their extra cost. Exteral hard disks ca be used as a storage locatio for both scheduled backups ad oe-time backups. Exteral hard disks possess the same set of advatages ad disadvatages as iteral hard disks with oe otable distictio: they ca be detached ad physically relocated more easily. Geerally speakig, though, this oly traslates ito a sigificat disaster recovery beefit if such disks are o some form of physical rotatio ito ad out of the data ceter. Tip: If iteral or exteral hard disks are used as a backup storage locatio, it is highly recommeded that such disks be dedicated for use solely with Widows Server Backup. Dedicatig a disk for Widows Server Backup usage precludes the disk from beig used for

94 Chapter 5 Widows Server 2008 Backup ad Restore 77 other types of file storage, but it affords several beefits relatig to recoverability ad iput/output (I/O) performace. See the Backig Up Your Server sectio of the Widows Server Backup help file for additioal details. Despite the fact that Widows Server 2008 icludes tape drive support, Widows Server Backup does ot support the targetig of tape drives for backup operatios. You caot place backups o USB flash drives or pe drives, either. Backup operatios must target oe of the four storage types. Whe weighig the decisio of the type of storage to use with Widows Server Backup, be sure to cosider the followig poits: Widows Server Backup caot back up files ad folders that total more tha 2040GB (roughly 2TB) per volume. This limitatio is based o the fact that a virtual hard drive (VHD) file is created at the backup destiatio for each volume that is backed up, ad VHD files themselves are limited to o more tha 2040GB i size. Because Widows Server Backup employs shadow copies for versioig, you must format backup storage locatios with NTFS. You caot use FAT32 o storage targets for backup operatios. Microsoft recommeds that storage locatios that support multiple backup versios be at least 1.5 times the size of the data beig backed up to eable the storage of a couple of backup versios. Additioal storage aturally allows for a greater umber of backup versios. Widows Server Backup does ot support backig up data from or storig backups o Clustered Shared Volumes. Data o such volumes must be hadled with somethig other tha Widows Server Backup. Because full server backups are typically performed to provide recovery optios i the evet of a catastrophic server failure or similar disaster sceario, the storage of backups o direct attached storage is cotraidicated. For Widows Server Backup, this meas you should strogly cosider the use of remote shared folders for your server backups to guaratee that backups are ot lost whe a server becomes uavailable or is impacted by a disaster. If the limitatio of a sigle backup per server per remote folder is too costraiig, a process that begis with a backup to a iteral or exteral hard disk supports the storage of multiple backup versios per server. This icreased flexibility comes with greater complexity, however. To esure the availability of required recovery data i a disaster sceario, it is ecessary to copy captured backups to a etwork locatio or replicated storage each time a backup is take. You ca perform such copies by schedulig custom scripts or usig third-party tools.

95 78 SharePoit 2010 Disaster Recovery Guide The storage locatio equatio is balaced somewhat differetly for idividual compoet backup ad restore. With the otable exceptio of AppCmd.exe the tools that are tied to the backup ad recovery of idividual compoets have relatively similar profiles ad trade-offs whe it comes to addressable storage locatios: AppCmd.exe. Limited to geeratig IIS cofiguratio backups withi the local %WINDIR%\ System32\ietsrv\backup directory. IetMgr.exe. Ca target both local ad etwork locatios for SSL certificate export ad import. Supports mapped drives ad Uiversal Namig Covetio (UNC) paths. Certificates MMC sap-i. Ca target both local ad etwork locatios for all certificate exports ad imports. Supports mapped drives ad UNC paths. Widows Server Backup. Supports local ad etwork locatios as described earlier. RegEdit.exe. Local ad etwork locatios ca be targeted for the export ad import of registry settigs. Supports mapped drives ad UNC paths. Placemet of backups o local storage is geerally more coveiet ad quick tha usig etwork storage, but it limits recovery whe the server is dow. Because the majority of the backup ad recovery scearios that are tied to idividual compoets deped o applicatios that are part of a fuctioal server ad file system ayway, the choice of whether to back up ad restore from local storage or etwork storage is really oe of preferece. The oly strog recommedatio is that the backup locatio or locatios be commuicated clearly ad applied cosistetly across servers to reduce cofusio if a restoratio must be performed. Backig Up Widows Server 2008 The tools that you have available to you out of the box, the targets that are of iterest, ad the major cosideratios related to backup plaig have all bee discussed. It is time to itegrate each of these topics ad actually carry out some backup operatios. Full Server Backup This sectio takes you through the process of establishig a daily full server backup schedule that targets a remote shared folder. This backup sceario is a relatively commo oe, ad it addresses may of the basic requiremets that exist for disaster recovery scearios ivolvig server recovery from a catastrophic evet. Before attemptig the followig series of steps, you must address the followig prerequisites: 1. Esure that Widows Server Backup Features are eabled, as described earlier i the sectio titled Eablig the Widows Server Backup Features. 2. Make sure your accout is a member of either the Admiistrators group or Backup Operators group o the local server beig backed up.

96 Chapter 5 Widows Server 2008 Backup ad Restore Create a service accout that is used whe executig the backup jobs that are created. This accout should also be a member of either the Admiistrators group or the Backup Operators group o the local server. 4. Have a remote shared folder that is olie, possesses sufficiet free space for your backup data, ad is accessible via UNC path for readig ad writig by both your accout ad the service accout created i step Esure that clustered shared volumes (distributed-access file system volumes that are ew to failover clusterig i Widows Server 2008 R2) are either the source or the destiatio for backup data. If you have addressed these cocers, you are ready to proceed. 1. Log o to the server that is to be backed up usig your accout credetials. 2. Click the Start butto ad avigate to Admiistrative Tools, Widows Server Backup. Doig so brigs up the Widows Server Backup MMC sap-i, as show i Figure Figure 5.23 The Widows Server Backup MMC sap-i. 3. Click the Backup Schedule lik uder the Actios meu o the right side of the meu to lauch the Backup Schedule Wizard. After a few momets with a progress bar, the Gettig Started page of the Backup Schedule Wizard appears with some basic iformatio about the wizard. Click the Next butto to cotiue. 4. The Select Backup Cofiguratio page appears. As show i Figure 5.24, you should select the Full Server (Recommeded) optio to capture all data o the server withi the backup.

97 80 SharePoit 2010 Disaster Recovery Guide Figure 5.24 Selectig the server s etire cotets for backup. Selectig the Full Server (Recommeded) optio affords you a great deal of flexibility i the evet of a disaster. With a full server backup, you could choose to recover the etire server, oly certai volumes o the server, system state iformatio, or ay combiatio of these items ad more. Click the Next butto to cotiue to the ext wizard page. 5. O the Specify Backup Time page, you select the time or times at which you wat Widows Server Backup to lauch a backup operatio. Figure 5.25 demostrates cofigurig a sigle daily backup that is executed at 2 a.m. each day. If Widows Server Backup represets the primary mechaism through which server data protectio is achieved, RPO targets that have bee established for the server eviromet should directly drive the frequecy with which you perform backups. You ca typically use a sigle daily backup to meet a 24-hour RPO target for server data, two evely spaced daily backups to meet a 12-hour RPO target, three evely spaced daily backups to meet a 8-hour RPO target, ad so o. Of course, you must balace the frequecy with which you take backups agaist the impact of ruig such backups. Coductig backups durig ormal busiess hours ca adversely impact server availability ad etwork utilizatio, so may orgaizatios choose to ru backups durig obusiess hours.

98 Chapter 5 Widows Server 2008 Backup ad Restore 81 Figure 5.25 Establishig a 2 a.m. daily backup schedule. I additio, backups do ot complete istataeously; they may take hours to ru. You must cosider this backup ru time whe determiig the frequecy with which to perform backups to avoid overlap betwee adjacet backups. Click the Next butto to cotiue oce you have specified your backup frequecy ad executio time(s). 6. The Specify Destiatio Type page appears ad prompts you to select the storage locatio type used to store your backups. Because this walk-through places backups o a shared etwork folder, the Back Up to a Shared Network Folder optio is selected, as show i Figure Note: As show i Figure 5.26, the wizard recommeds that a dedicated hard disk, either iteral or exteral, be utilized as a storage locatio for backups. Dedicatig a disk permits multiple backup versios ad removes the depedecy of a fuctioig etwork, but it does ot offer a built-i mechaism for offloadig or migratig backup data i the evet of a catastrophic server failure. If you elect to take the dedicated disk route, your implemetatio should also iclude a custom script or migratio strategy to trasfer backups to a safe locatio i accordace with your disaster recovery strategy ad larger busiess cotiuity pla (BCP).

99 82 SharePoit 2010 Disaster Recovery Guide Figure 5.26 Selectig a shared etwork folder for backups. 7. Oce you have specified the destiatio type, click the Next butto to cotiue. A message box appears to war you that each backup to a remote shared folder erases ay that were previously preset. Click the OK butto to cotiue. 8. The Specify Remote Shared Folder page appears ad prompts you for the UNC path of the remote shared folder to create backups. It is here that you supply the predetermied file share locatio, as show i Figure Tip: Because the backup is performed to a remote share, the oly Access Cotrol optio is Iherit. This meas that ayoe with access to the file share where the backup data is writte ca see the data, work with it, ad eve delete it. Therefore, it is strogly recommeded that the backup destiatio locatio be locked dow to just a select group of admiistrators ad the service accout uder which the backup jobs are executed. 9. Oce you have specified the backup locatio, click the Next butto. The Register Backup Schedule dialog box appears to prompt you for the credetials uder which the backup jobs should be ru. It is here that the service accout credetials, which were created i prerequisite step 3, are supplied. Oce you have supplied the backup service accout credetials, click the OK butto to cotiue.

100 Chapter 5 Widows Server 2008 Backup ad Restore 83 Figure 5.27 Specifyig the backup locatio. 10. The Cofirmatio page of the wizard appears, as see i Figure Cofirm that the details are correct, ad click the Fiish butto. 11. The Summary page appears, ad the wizard establishes ad schedules a recurrig backup job accordig to the parameters supplied. Whe it has fiished its actios, click the Close butto to close the wizard. 12. Oce you have closed the wizard, the Widows Server Backup sap-i updates to reflect that a backup schedule has bee created, as show i Figure Note the additio of the Scheduled Backup pae at the bottom of the mai widow, as well as the chage i status uder the Next Backup area i the middle of the widow. The completio of step 12 meas that your server has bee set up to ru daily backups o the schedule specified. A actual backup has ot yet bee ru, though. Ideally, you should validate that a backup ca be ru give all the cofiguratio data that was just supplied to create the scheduled task. With a scheduled backup, it is a simple matter to go through the Backup Oce Wizard withi the Widows Server Backup sap-i, idicate that you wat to ru a sigle backup usig the parameters you just supplied through the Backup Schedule Wizard (as show if Figure 5.30), ad execute a oe-time backup task to perform validatio by clickig the Backup butto.

101 84 SharePoit 2010 Disaster Recovery Guide Figure 5.28 Cofirmig the backup schedule parameters. Figure 5.29 Widows Server Backup sap-i updated to reflect backup schedule.

102 Chapter 5 Widows Server 2008 Backup ad Restore 85 Figure 5.30 Lauchig a oe-time backup usig scheduled backup optios. After you have started the oe-time backup, the display of the Backup Oce Wizard chages to provide a detailed status for moitorig the backup operatio, as show i Figure You ca close the Backup Oce Wizard after the backup is complete or at ay poit prior to completio. If you close the wizard prior to backup completio, the backup simply cotiues to ru i the backgroud util it is complete. Idepedetly of the Backup Oce Wizard, the Messages widow withi the Widows Server Backup sap-i updates to reflect both the backup job s progress ad its ultimate success or failure. The Status displays below the Messages widow also chage to icorporate the status of the most recetly attempted backup operatio. Assumig the backup job completes successfully, you have the data eeded to fully recover the server i the evet of a catastrophic failure. Idividual Compoet Backup Whereas full server backups capture the cotets of a etire server to provide recovery optios i the evet of a catastrophic failure, the scope ad beefits of a idividual compoet backup are more specific i ature. These backups commoly provide some form of rollback support ad guard agaist uwated cofiguratio chages should somethig go awry durig a operatio such as a upgrade, a patch cycle, or the rollout of ew solutio packages to the farm.

103 86 SharePoit 2010 Disaster Recovery Guide Figure 5.31 Moitorig the backup job from the Backup Oce Wizard. Idividual compoet backups, ad their associated recovery operatios, usually require that the server already be operatioal ad i good geeral health. This precoditio is assumed for each of the backup procedures that follow. Files ad File Folders Backig up files ad folders o the server etails usig the Widows Server Backup sap-i ad a process that is similar to the oe described previously for a full server backup. The prerequisites for a full server backup apply here, as well, but with oe otable exceptio: o service accout is eeded, as described i prerequisite 3. Note: Although this specific walk-through details a oe-time backup of files ad folders o the server, it is certaily possible to establish a scheduled backup for these items. Aytime a scheduled backup is established, it is cosidered a best practice to ru the scheduled job withi the cotext of a service accout. For oe-time backups, however, backup operatios are coducted directly from the cotext of your user accout. Oce you have addressed all prerequisites, you are ready to proceed. 1. Log o to the server that is to be backed up usig your accout credetials.

104 Chapter 5 Widows Server 2008 Backup ad Restore Click the Start butto ad avigate to Admiistrative Tools, Widows Server Backup. Doig so brigs up the Widows Server Backup MMC sap-i, as show previously i Figure Click the Backup Oce lik uder the Actios meu o the right side of the meu to lauch the Backup Schedule Wizard. After a few momets with a progress bar, the Gettig Started page of the Backup Schedule Wizard appears with some basic iformatio about the wizard. Click the Next butto to cotiue. 4. The Backup Oce Wizard appears as show i Figure If oe or more scheduled backup jobs exist, the Scheduled backup optios selectio is available. The selectio of iterest for this exercise, however, is the Differet Optios selectio. Choose this optio butto ad click the Next butto to cotiue. 5. You are prompted to select either a Full Server or a Custom backup, as show i Figure Select the Custom optio to specify a subset of folders ad files, ad the click the Next butto to cotiue. Figure 5.32 Selectig the backup cofiguratio. 6. The Select Items for Backup page appears as show i Figure It is here that files ad folders are selected as backup targets. Iitially, o files ad folders are selected. Click the Add Items butto to begi the selectio process.

105 88 SharePoit 2010 Disaster Recovery Guide Figure 5.33 Items that are selected for backup. Note: The Advaced Settigs butto affords you some additioal cotrol over the backup operatio, icludig the optio to specify backup exclusios ad the ability to idicate how applicatio log files should be hadled by the Volume Shadow Copy Service (VSS) durig the backup operatio. The default settigs for these optios are sufficiet for oetime backups, but ivestigate the Advaced Settigs if you desire greater cotrol for the areas metioed. 7. The Select Items dialog box appears, as show i Figure It is here that you ca specify files, folders, system state, ad additioal backup targets. I this example, all the files i the GAC (at C:\Widows\assembly) are selected for a oe-time backup. Oce the GAC has bee selected, the OK butto is clicked to cotiue. 8. The Select Items dialog box closes, ad the Select Items for Backup page (Figure 5.33) becomes active agai. At this poit, the list of items for backup ow icludes the C:\Widows\assembly folder. Click the Next butto to cotiue. 9. You are prompted to select oe of the local drives or a remote shared folder as destiatio for the backup, as show i Figure Select the Remote Shared Folder optio, ad click the Next butto to cotiue. 10. The Specify Remote Folder dialog box appears. It is here that a etwork share is specified as a destiatio for the backup. I additio to selectig a remote folder, you must

106 Chapter 5 Widows Server 2008 Backup ad Restore 89 Figure 5.34 Selectig items to be backed up. Figure 5.35 Specifyig the backup destiatio type.

107 90 SharePoit 2010 Disaster Recovery Guide specify oe of two Access cotrol optios. The Iherit optio is selected by default, ad it leaves the permissios of the remote share ad created subfolders itact durig the backup. If the Do Not Iherit optio is selected, Widows Server Backup attempts to restrict access to the WidowsImageBackup subfolder that is created withi the specified locatio to a sigle user accout. For the purposes of this exercise, the default Iherit optio is selected, alog with the remote share (as show i Figure 5.36). Click the Next butto to cotiue. Figure 5.36 Specifyig the remote share for backup. 11. If the remote share already cotais a backup for the curret server, either scheduled or oe-time, a warig dialog box appears to iform you that the backup operatio that is about to be performed will overwrite the existig backup. Click the OK butto to cotiue. 12. The Cofirmatio page of the Backup Oce Wizard appears, as show i Figure Validate the selectio you have made, ad click the Backup butto to begi the backup process. 13. A Backup Progress dialog box similar to the oe show i Figure 5.31 appears. As the backup operatio rus, the progress beig made is reflected o the form. You ca close the dialog box at ay time durig the actual backup operatio, or you ca wait util the backup has completed i its etirety before closig it. If the dialog box is closed prior to the completio of the backup operatio, the backup cotiues i the backgroud util it completes.

108 Chapter 5 Widows Server 2008 Backup ad Restore 91 Figure 5.37 Cofirmatio of backup selectios. IIS Cofiguratio Creatig a backup of the IIS7 cofiguratio files is a relatively straightforward affair provided the Path eviromet variable has bee updated to iclude the %WINDIR%\System32\ietsrv path, as described earlier i Path Cosideratios uder the Backup Prerequisites sectio. 1. Ope a PowerShell widow by opeig the Start meu ad avigatig to All Programs, Accessories, Widows PowerShell, Widows PowerShell. 2. Type appcmd.exe add backup <ame4, where <ame4 is replaced by the ame you wat to give the backup file set. After you have etered the full commad, press the Eter key to execute the backup. 3. Whe the backup is complete, you are preseted with a status message similar to the oe show i Figure Close the PowerShell widow by typig exit ad pressig the Eter key. The backup that you have created ca be left i place or moved to a alterate locatio as eeded. By default, the backup is i a directory withi the %WINDIR%\System32\ietsrv \backup folder that matches the ame you specified i step 2. Figure 5.39 demostrates this for the example show earlier.

109 92 SharePoit 2010 Disaster Recovery Guide Figure 5.38 Successful executio of a IIS cofiguratio backup. Figure 5.39 IIS7 cofiguratio backup folder ad cotets. Note: Microsoft s TechNet documetatio for SharePoit 2010 recommeds agaist usig metabase backup to protect IIS settigs. Istead, Microsoft recommeds maual documetatio of all IIS cofiguratio settigs or the use of a tool (such as Microsoft System Ceter Cofiguratio Maager) to automate the process. Because IIS7 s cofiguratio backup files are XML, they are still largely huma-readable meaig that eve if you elect ot to use them for direct restore purposes, you ca still examie them to extract a sigificat quatity of cofiguratio iformatio. At the ed of the day, simply make sure you have a pla i place for how you ited to use your backup files, ad test that pla regularly.

110 Chapter 5 Widows Server 2008 Backup ad Restore 93 SSL Certificates SSL certificates are commoly backed up i visual fashio usig either the Certificates MMC sap-i or the IIS Maager sap-i. The example that follows demostrates the latter approach, although both lead to the same edpoit. 1. Start the Iteret Services Maager by opeig the Start meu ad avigatig to Admiistrative Tools, Iteret Iformatio Services (IIS) Maager. 2. Whe the IIS Maager starts, locate the Start Page root ode i the Coectios Tree- View cotrol o the left side of the sap-i. Select the ode represetig the curret server that appears just below the Start Page ode. I the example show i Figure 5.40, the curret server is SPDEV. Figure 5.40 The IIS Maager sap-i. 3. Whe the curret server ode is selected, the cetral task pae i the sap-i is populated with various ASP.NET, IIS, ad Maagemet Features. Locate the Server Certificates Feature uder those listed for IIS, ad double-click it. 4. The cetral task pae shifts to display Server Certificates, as show i Figure Each lie i the cetral task pae represets a SSL certificate that is istalled ad available for use by IIS7. Select the oe that you wat to back up by clickig o it, ad the click the Export lik that appears uder Actios o the right side of the sap-i.

111 94 SharePoit 2010 Disaster Recovery Guide Figure 5.41 Server Certificates. 5. The Export Certificate dialog box appears, as show i Figure 5.42, ad you are prompted to select a file ame ad a password for the exported certificate. Specify these values, ad the click the OK butto to execute the export. Figure 5.42 Specifyig the certificate export parameters.

112 Chapter 5 Widows Server 2008 Backup ad Restore 95 Note: You are prompted for a password, because the certificate you select is exported with its private key data. Ay server possessig the private key for a certificate may act ad respod as the server amed by the certificate, so aturally it is importat that ay certificate export that cotais private key data is protected. 6. The export executes ad completes without cofirmatio. To verify that the export succeeds, browse to the locatio you selected for your export, ad verify that the appropriate certificate export file is preset, as show i Figure Figure 5.43 Verifyig the certificate export. Widows Registry You accomplish exports of the Widows Registry usig the Registry Editor tool. This example exports the HKEY_LOCAL_MACHINE brach of the Registry to the local file system. 1. Ope the RegEdit.exe tool by clickig Start ad selectig Ru. Whe the Ru dialog opes, type regedit.exe ad click the OK butto. 2. The Registry Editor tool appears, as show i Figure Locate the HKEY_LOCAL_ MACHINE ode uder the Computer root ode i the left TreeView cotrol, ad select it by clickig o it.

113 96 SharePoit 2010 Disaster Recovery Guide Figure 5.44 The Registry Editor tool. 3. Click o the File meu at the top of the Registry Editor widow ad select the Export optio. A dialog box pops up, as show i Figure Figure 5.45 Specifyig export iformatio for the selected Registry brach.

114 Chapter 5 Widows Server 2008 Backup ad Restore Specify path ad file ame iformatio for the export file, ad click the Save butto. The Registry Editor carries out the requested export without cofirmatio or a idicatio of completio. To verify that the export was successful, browse to the specified destiatio, as demostrated i Figure Figure 5.46 Successful Registry export. Restorig Widows Server 2008 Whe questioed, most admiistrators idicate that they perform some type of server backup o a regular basis. Whe that same group of admiistrators is asked if they frequetly test their recovery operatios for the systems beig backed up, the percetage of those respodig yes teds to drop to a alarmigly low level. Simply put, it is ot eough to execute backups ad hope that recovery proceeds without issue i the evet of a disaster. The time to discover that recovery is ot possible or that a backup strategy is isufficiet is ot whe you eed recovery. Test recovery operatios regularly to esure that they work whe eeded. Full Server Recovery This exercise assumes the catastrophic loss of the server that was fully backed up i the previous Full Server Backup sectio. This sectio walks you through the recovery of that server usig the backup that was created.

115 98 SharePoit 2010 Disaster Recovery Guide First, a word of cautio: the Widows RE greatly simplifies the process of brigig back a server followig catastrophic failure, but full server recovery is a iexact sciece. Oftetimes there are hardware differeces betwee the server that was backed up ad the server upo which recovery is beig attempted. For example, hard drive couts ad capacities may vary, RAID cotrollers may differ, etwork cards may be differet, ad more. Potetial hardware differeces ad other variatios may require you to adapt the full recovery process described ext. At a miimum, be sure to practice the recovery of your servers at regular itervals ad accurately documet the details of the restoratio process. Before you attempt ay sort of full server recovery, you must address a umber of prerequisites: 1. You must have a test server with characteristics that are very similar to the server that was fully backed up. Ideally, the test server should have hardware that is idetical to the server that was backed up. Some differeces ca be tolerated fairly well, such as the test server possessig hard drives of greater capacity tha those i the source (backup) server. Other differeces are ot tolerated at all, such as tryig to restore a x64-based backup to x86-oly hardware. As a rule of thumb, the greater the umber ad type of differeces betwee the source server ad the backup server, the greater the likelihood of ecouterig problems durig recovery. Tip: Virtual machies ca be used to great effect whe testig recovery plas. Widows Server 2008 icludes Hyper-V for virtualizatio. If you are ot familiar with Hyper-V, cosider checkig it out. 2. You must possess accout credetials that ca be used to access the remote shared folder where the target server backup is stored. 3. You must have access to a Widows Server 2008 istallatio DVD, a bootable istallatio thumb drive, or some other bootable mechaism that affords you access to the Widows RE. If you are attemptig to recover a x64 eviromet, you must use the x64 versio of the Widows RE. By the same toke, x86 recoveries require the x86 Widows RE. 4. Esure that clustered shared volumes are either the source or the destiatio for ay backup data. If you have addressed these cocers, you are ready to proceed with recovery. 1. Start your server ad boot from the media cotaiig the Widows RE. Your server should automatically go ito the Widows Is Loadig Files scree with a progress bar at the bottom shortly after bootig. If this does ot occur, or the server attempts to boot from aother source (such as a residual hard drive image), you may eed to access the oe-time boot meu optio that is commoly available o servers. Usig such a boot meu allows you to specify the server s boot locatio, be it a DVD, a USB locatio, or somethig else.

116 Chapter 5 Widows Server 2008 Backup ad Restore After the server has booted from the desired media, you are preseted with the Istall Widows scree. Esure that you select the desired istallatio laguage, time ad currecy formats, ad iput method before clickig the Next butto to cotiue. 3. You are preseted with the widow show i Figure Although the Istall Now optio is frot ad ceter i the widow, the area of iterest is i the lower-left portio of the widow. Click o the Repair Your Computer lik to cotiue. Figure 5.47 The Istall Widows scree. 4. You are preseted with the System Recovery Optios dialog box show i Figure Esure that the Restore Your Computer Usig a System Image That You Created Earlier optio is selected, ad click the Next butto to cotiue. 5. Neither a iteral or exteral hard drive cotaiig a system image is attached to the server, so you are wared that a system image caot be foud o the computer. Click the Cacel butto to dismiss the dialog box. 6. Because a system image is t available locally, the oly optio that is available o the Re-Image Your Computer dialog box (show i Figure 5.49) is Select a System Image. Click the Next butto to cotiue. 7. You are prompted to select the locatio of the backup you wat to restore, as show i Figure Because you eed to poit the Widows RE at the remote share housig your system image, you eed to click the Advaced butto i the lower-left portio of the scree to guide the tool to a etwork-based image.

117 100 SharePoit 2010 Disaster Recovery Guide Figure 5.48 System Recovery Optios. Figure 5.49 The Re-Image Your Computer dialog box.

118 Chapter 5 Widows Server 2008 Backup ad Restore 101 Figure 5.50 Selectig a locatio cotaiig the backup that is to be restored. 8. The dialog box show i Figure 5.51 appears. Select the Search for a System Image o the Network optio to cotiue. Figure 5.51 Specifyig a system image o the etwork. Note: Although the Widows RE cotais drivers for a sigificat umber of etwork adapters, you may discover that you are uable to browse or specify a etwork locatio without first loadig drivers for your server s specific adapter or adapters. If this is the case, select the Istall a Driver optio ad follow the istructios to load drivers for your etwork adapter or adapters before attemptig to proceed.

119 102 SharePoit 2010 Disaster Recovery Guide 9. You are wared that coectig to a etwork may leave your server vulerable, ad you are asked to cofirm the coectio. Click the Yes butto to cofirm ad cotiue. 10. You are prompted to specify the etwork locatio where the system image that is used for restoratio resides. As show i Figure 5.52, specify the UNC path to the image that was previously created durig the full server backup process, ad click the OK butto to cotiue. Figure 5.52 Supplyig the UNC path to the recovery image. 11. You are prompted to supply the credetials of the accout you wat to use whe accessig the remote share specified i the previous step. Supply the userame ad password desired, esurig that you iclude a domai qualifier (i the form of domai\userame or userame@domai) for the userame if eeded. Oce you have supplied the credetials, click the OK butto to cotiue. 12. The backup locatio dialog box reappears, as show i Figure Provided the etwork locatio specified previously i step 10 cotaied a recogizable system image, the grid i the dialog box ow cotais a populated row. Esure that the row is selected, ad click the Next butto to cotiue. 13. You are prompted to select the date ad time of the system image you wat to restore. Because a remote shared folder ca house oly a sigle image per server, just oe etry is available for selectio, as show i Figure Select it ad click the Next butto to cotiue. 14. The restore optios dialog appears, as show i Figure For a server with uformatted hard disks or with hard disks that do ot have system volume iformatio matchig the system image that is beig restored, the Format ad Repartitio Disks optio is selected ad grayed out as show. Because a full recovery is beig performed ad it is desirable to restore all data volumes i additio to the system drives, esure that the Oly Restore System Drives check box remais uchecked. Click the Next butto to cotiue.

120 Chapter 5 Widows Server 2008 Backup ad Restore 103 Figure 5.53 Backup image available for recovery. Figure 5.54 Selectig the available system image.

121 104 SharePoit 2010 Disaster Recovery Guide Figure 5.55 Choosig additioal restore optios. Note: Similar to step 8, there is a possibility that you may have to load additioal drivers for Widows RE to see all the hard drives attached to your system. If this is the case, click the Istall Drivers butto, ad follow the istructios preseted before attemptig to advace from the Choose Additioal Restore Optios dialog box. 15. A basic cofirmatio dialog box appears so that you ca verify your recovery selectios. Click the Fiish butto to cotiue with the recovery. 16. A message box pops up to war you of the impedig hard drive reformattig. Click the Yes butto to ackowledge the warig ad cotiue. 17. The recovery process begis, ad a message box trackig the progress of the restoratio appears, as show i Figure As stated i the message box, the recovery operatio may take aywhere from a few miutes to a few hours. The amout of time take depeds o the amout of data to be restored, the speed of your etwork coectio, the speed of your server s hard drives, ad a umber of other factors. 18. Oce the recovery operatio has completed, the restart dialog box appears, as show i Figure If you take o actio, the server automatically restarts after a miute ad boots ito the restored operatig system. As stated earlier, full server recovery is a iexact sciece. If the recovery operatio fails the first time for uforesee reasos, cosider tryig it agai with slightly differet recovery parameters.

122 Chapter 5 Widows Server 2008 Backup ad Restore 105 Figure 5.56 Trackig the progress of the recovery. Figure 5.57 Restartig the server followig recovery. Sometimes reformattig hard drives, restorig oly the system drive o the first pass, or perhaps excludig a extra disk from withi the restore optios dialog box ca make the differece betwee a restoratio error ad a successful recovery operatio. Restorig Idividual Compoets Each of the recovery activities described here assumes that you have completed its correspodig backup activity. For example, the IIS Cofiguratio restore utilizes the folder of files created i the IIS Cofiguratio idividual compoet backup exercise. Files ad File Folders Restorig files ad folders o the server etails usig the Widows Server Backup sap-i ad a process that is similar to the oe described previously for a full server recovery. The prerequisites for a full server recovery apply here; you must also esure that your accout has read access to the backup files you ited to restore. Oce all prerequisites have bee addressed, you are ready to proceed. 1. Log o to the server that you ited to restore files to usig your accout credetials.

123 106 SharePoit 2010 Disaster Recovery Guide 2. Click the Start butto ad avigate to Admiistrative Tools, Widows Server Backup. Doig so brigs up the Widows Server Backup MMC sap-i, as show previously i Figure Click the Recover lik uder the Actios meu o the right side of the meu to lauch the Recovery Wizard. After a few momets with a progress bar, the Gettig Started page of the Recovery Wizard appears with some basic iformatio about the wizard. You are also prompted to idicate whether your backup files are stored o the server or i aother locatio. Because the backup is stored o a remote share, select the secod optio, as show i Figure 5.58, ad the click the Next butto to cotiue. Figure 5.58 Specifyig a backup storage locatio for restore operatios. 4. The Specify Locatio Type page of the wizard appears, ad you are prompted to idicate whether the target backup is stored o a local drive (iteral or exteral) or a remote share. Select the Remote Shared Folder optio, as show i Figure 5.59, ad click the Next butto to cotiue. 5. You are prompted to select the remote share where the backup file set is located. Specify the UNC path to the backup share, as show i Figure 5.60, ad click the Next butto to cotiue.

124 Chapter 5 Widows Server 2008 Backup ad Restore 107 Figure 5.59 Selectig the backup locatio type. Figure 5.60 Idetifyig the UNC path of the remote share housig the backup files.

125 108 SharePoit 2010 Disaster Recovery Guide Note: If you are preseted with a dialog box promptig you to specify the credetials of a user who has read access to the etwork share, it meas that your accout does t possess the rights eeded to access the locatio. Either supply the credetials of a accout that does have access to the locatio, or verify that you have specified the proper remote share iformatio. 6. You are prompted to select the date ad time of the backup set that will be used for restore operatios, as show i Figure Because remote shares ca be used oly to store a sigle backup set per server, oly a sigle date ad time will be available for selectio. Click the Next butto to cotiue. Figure 5.61 Selectig the date ad time of the backup to be used. 7. The Select Recovery Type page of the Recovery Wizard appears, as show i Figure 5.62, ad you are preseted with the optio of restorig either specific files ad folders or a etire volume. The remaiig two optios are grayed out because applicatio ad system state iformatio was ot captured by the origial backup operatio. Because oly the GAC was backed up, select the first optio (Files ad Folders), ad click the Next butto to cotiue. Note: The optio to restore a etire volume is somewhat deceptive i the case of the backup that was performed. If this optio is selected, you are evetually told that oly a

126 Chapter 5 Widows Server 2008 Backup ad Restore 109 subset of files had bee backed up ad that oly they ca be restored. The restore operatio obviously caot recover files that were ot part of the origial backup. Figure 5.62 Specifyig the type of recovery to perform. 8. O the Select Items to Recover page, you are give the optio to specify the files ad folders you wat to restore durig the recovery operatio. You select a folder uder the Available Items pae o the left, ad that folder ad all its files ad subfolders are selected for recovery o the right. I the case of Figure 5.63, you ca see that three differet folders were captured durig the backup operatio ad are selected for recovery. Note: Wait a miute, you might be sayig, Oly the GAC was selected durig the backup operatio. Why do I see additioal folders besides the C:\Widows\assembly folder listed for possible recovery? Good questio! The GAC is actually a special folder, ad it operates somewhat similarly to the ew libraries that are available i Widows Server 2008 R2 ad Widows 7. Whe you are lookig at the GAC withi Widows Explorer, you are actually lookig at a listig of.net assemblies, ative images, policy files, ad other elemets that exist i a variety of differet locatios withi the file system. May of the items are located at the C:\Widows\assembly path as you would expect, but some of the listed items are located i applicatio directories ad other locatios withi the Widows folder. While backig up the GAC, Widows Server Backup was smart eough to pull i all the files that were reflected through the GAC. Pretty eat, huh?

127 110 SharePoit 2010 Disaster Recovery Guide Figure 5.63 Selectig the files ad folders that will be recovered. 9. You are prompted to idicate how the recovery should proceed o the Specify Recovery Optios page, as show i Figure Whe recoverig idividual files ad folders, you do ot have the optio to automatically restore to the origial locatio from which Figure 5.64 Specifyig the recovery optios.

128 Chapter 5 Widows Server 2008 Backup ad Restore 111 the files ad folders were captured. You eed to specify the actual path where restored folders ad files are placed. Tip: Although you caot choose to automatically have the Recovery Wizard place the restored files back i their origial locatios, there is geerally o barrier to usig the Browse butto to maually select the appropriate top-level folder to force the files back to their origial locatios. This geerally works without issue, but exercise care for system directories ad some applicatio directories where some target files may be locked or owritable. You also have cotrol over how potetial file collisios are hadled ad whether file ad folder permissios are applied from the origial backup locatio or iherited from the recovery destiatio. 10. Before the recovery begis, you are asked to review the recovery selectios you have made o the Cofirmatio page, as show o Figure Whe you are satisfied with the selectios, click the Next butto to begi the recovery. Figure 5.65 Cofirmig the recovery selectios. 11. The page chages to allow you to moitor the progress of the recovery operatio, as show i Figure You ca close this wizard at ay time prior to or after the

129 112 SharePoit 2010 Disaster Recovery Guide Figure 5.66 Moitorig recovery progress. completio of the recovery by clickig the Close butto. If the Recovery Wizard is closed prior to completio, the recovery cotiues i the backgroud. 12. Upo completio of the restore operatio, the files ad folders that were selected for recovery are foud uder the E:\temp path, as specified i step 9. As show i Figure 5.67, the folder structure uder E:\temp mirrors the folder structure of the GAC ad the refereced locatios that were captured as part of the origial backup. With files recovered i E:\temp, you are free to copy them to their origial locatios o the server or use them elsewhere as eeded. IIS Cofiguratio Restoratio of a previous set of IIS cofiguratio files is icredibly easy as log as the desired backup folder is placed i the %WINDIR%\System32\ietsrv\backup folder either maually or through the actio of the IIS cofiguratio backup described earlier ad show i Figure If the backup is preset i the aforemetioed folder, use the followig steps to restore it: 1. Ope a PowerShell widow by opeig the Start meu ad avigatig to All Programs, Accessories, Widows PowerShell, Widows PowerShell.

130 Chapter 5 Widows Server 2008 Backup ad Restore 113 Figure 5.67 Recovered folders ad files. 2. Type appcmd.exe restore backup <ame4, where <ame4 is replaced by the ame of the cofiguratio file backup set that is beig restored. After you have etered the full commad, press the Eter key to execute the restore. 3. Whe the restore is complete, you are preseted with a status message similar to the oe show i Figure Figure 5.68 Successful restoratio of a IIS cofiguratio. 4. Close the PowerShell widow by typig exit ad pressig the Eter key.

131 114 SharePoit 2010 Disaster Recovery Guide SSL Certificates As with the SSL certificate backup process, restoratios are typically carried out usig either the Certificates MMC sap-i or the IIS Maager sap-i. The restoratio example that follows demostrates the latter approach ad assumes that you carried out the SSL certificate backup process illustrated earlier i the chapter. 1. Carry out steps 1 through 3 as described i the SSL certificate backup example to arrive at the Server Certificates widow, as show i Figure Click the Import lik uder the Actios optios o the right side of the widow. This brigs up the Import Certificate dialog box. 3. Specify the fully qualified path to the certificate file you are importig, ad provide the password that was supplied at the time of certificate export. Whe the fields have bee filled out as demostrated i Figure 5.69, click the OK butto to cotiue. Figure 5.69 Populatig the Import Certificate dialog box. Note: Uless you have specific security cocers or reasos for blockig future exports of the SSL certificate, it is recommeded that you allow the check box for certificate export to remai checked. This is the default. Ucheckig the box meas that you are o loger able to export the certificate ad have to rely o exteral backup copies i the evet that you wat to copy the certificate, migrate it, reistall it, or take some actio that would ivolve brigig the certificate outside the certificate store. 4. The import executes ad completes without cofirmatio of ay sort. To verify that the import has succeeded, simply verify that the certificate is preset i the mai pae of the Server Certificates widow i Figure 5.41.

132 Chapter 5 Widows Server 2008 Backup ad Restore 115 Widows Registry The easiest way to restore exported Registry settigs is to double-click a Registry export file ad click the Yes butto o the warig dialog that appears, as show i Figure Figure 5.70 Warig that appears whe mergig a.reg file with existig Registry settigs. Tip: A alterative to double-clickig the file is to right-click o it ad select the Merge optio from the cotext-sesitive meu that appears. Oce you select Yes, a merge is performed i the backgroud. Whe the merge actio is complete, you are otified with a dialog box idicatig whether the operatio was completed successfully or ecoutered issues. Coclusio The Widows Server 2008 operatig system is the foudatio of your SharePoit eviromet. Every server i your farm must be ruig it as its base operatig system. You eed to preserve the key elemets of your SharePoit farm stored withi the operatig system to have a solid, comprehesive disaster recovery solutio for your orgaizatio s SharePoit resources. If you do t take care to iclude these items i your backup ad restore plas, at a miimum you re icurrig additioal time ad resources spet to re-create them. Or, eve worse, you may ot be able to re-create them ad stad to lose valuable cofiguratio details ad resources. A commo theme that rus through the topic of SharePoit disaster recovery is the otio of layered protectio, ad this cocept exteds to the Widows server operatig system as well. You ca achieve catastrophic protectio of the server ad its cotets usig the Widows Server Backup Features that are built ito Widows Server Widows Server Backup provides ed-to-ed protectio, ad together with the Widows RE ca be used to perform a bare metal restore of a server. I additio to Widows Server Backup, the operatig system icludes a umber of tools you ca use to provide additioal protectio agaist commo occurreces such as file deletios,

133 116 SharePoit 2010 Disaster Recovery Guide miscofiguratio, ad other ocatastrophic issues. The list of tools icludes the Registry Editor, IIS Maager, ad AppCmd.exe amog others; you ca use each tool to back up ad restore a specific type of data or target withi the operatig system. These tools augmet Widows Server Backup rather tha replacig it. Aother best practice previously metioed i this guide that is especially relevat to this topic is the creatio, maiteace, ad review of a detailed chage log for the servers i your SharePoit eviromet. It ca quickly become difficult, if ot impossible, to build a accurate picture of what has bee istalled, modified, or removed from your servers if you do t record those updates. Although a full server recovery ca retur a server to a predefied poit i the past, such a recovery is seldom carried out uless a total system failure is ecoutered. Havig a accurate chage log ca be a ivaluable asset whe you are attemptig to restore a server s cofiguratio or data with tools that target idividual compoets ad through meas other tha a full server recovery. You should also keep i mid that a curret chage log does you little good uless you kow where idividual compoets backups ad other assets are stored. Although it is all too easy to store these files wherever you please or just delete them whe you re doe with them, this ca pose a serious risk to your system i the evet of a disaster. You should store these crucial files i a cotrolled, cetralized locatio so that you kow exactly where to fid them ad exactly which versio to use to redeploy the correct update. Make sure that the proper persoel ca access the locatio as eeded whe you must carry out recovery operatios. Now that you ve leared more about backig up ad restorig SharePoit-related items withi Widows Server 2008, you should be able to aswer the followig questios. You ca fid the aswers to these questios i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at 1. What is the SharePoit Root? 2. Ca the Widows Server Backup Features write backups to tape devices? 3. What is the Widows RE? 4. How ca you back up the IIS cofiguratio files? 5. What is a bare metal restore?

134 6 Widows Server 2008 High Availability I This Chapter Load Balacig High Availability I the mid-1970s, the Uited States Air Force (USAF) itroduced a ew aircraft desiged to provide U.S. forces o the groud with close-i air support, the A-10 Thuderbolt II, affectioately kow as the Warthog. The A-10 is ot a sleek, sexy fighter jet like the F-22 Raptor or F-15 Eagle, or is it techologically advaced like the B-2 Stealth bomber. It is t pretty, but it s effective. The A-10 is slow, as least compared to burers like the Raptor, ad it s far less maeuverable. This meas it s exposed to couterattacks for loger periods tha its fighter brethre, ad these attacks come i a much higher volume, meaig that the highest priorities i its desig were reliability ad durability. Every system i the A-10 critical to keepig it i the air has redudat backups available i case of a error or failure. This is just oe aspect of the thought that has goe ito keepig the A-10 safely i the air for as log as possible. The approach works; A-10s have bee hit by missiles ad hudreds of shells ad kept o tickig o coutless occasios. They ve eve flow home missig half a wig ad survived. You may be askig yourself, What does this have to do with Widows Server 2008 high availability (HA)? Hopefully, the brief descriptio of the A-10 s redudat desig ad durability has gotte you thikig about the steps you could take to itroduce similar attributes ito your Share- Poit eviromet. What sort of redudat systems do you, or should you, have i place if a key compoet of your system should fail? I Chapter 5, Widows Server 2008 Backup ad Restore, you were itroduced to some of the ways you ca back up ad restore items i Widows Server 2008 that are crucial to SharePoit. This chapter outlies several ways you ca create redudat systems for your SharePoit eviromet so that if a hard drive, server, or more should fail, your users ca still access, modify, ad work with their busiess-critical SharePoit cotet. HA is ot a term that this book has discussed i great detail yet, but it s a itegral part of a comprehesive disaster recovery system. HA refers to the ability of a techology platform, system, or eviromet to remai olie ad available i the face of outages or failures by oe or more of its costituet subsystems. 117

135 118 SharePoit 2010 Disaster Recovery Guide It is pretty much physically impossible ad all too ofte fiacially urealistic for a system such as your SharePoit eviromet to be 100 percet available all day, 365 days a year. Desigig ad egieerig for HA meas that the system is built to be fully available for a give percetage of time, such as 95 percet, 99 percet, or percet (also referred to as havig five ies of uptime) ad withstad uplaed situatios such as a hard drive failure, a etwork outage, or a power outage rederig a etire dataceter ioperable. HA is ot somethig that is easy to implemet, or is it a problem you ca solve by a sigle hardware or software solutio. It requires comprehesive aalysis, plaig, ad desig of your iformatio techology (IT) ifrastructure from the groud up, ot to metio careful cosideratio of your service ad uptime requiremets, the budget you have available to meet those requiremets, as well as the staff eeded to maage ad implemet your HA processes. Although uptime umbers such as the five ies may be attractive to you ad your maagemet, the overhead associated with providig that kid of service is ofte prohibitive to all but the largest of eterprises. The importat thig to do is to review the optios discussed i this chapter, determie the HA solutio that best fits your eeds ad budget, ad the make sure your service levels are clearly defied ad commuicated to your customers. If you take away oe thig from this chapter about Widows Server 2008 HA, keep this i mid: there is o oe solutio that is goig to make your SharePoit eviromet ad its ifrastructure highly available from top to bottom. It takes a combiatio of hardware, software, cofiguratio, repeatable ad stable procedures, ad maiteace to achieve this goal for most platforms, ad SharePoit is o differet due to the flexibility of how you ca cofigure it ad its geeral overall complexity. You eed to hadle differet pieces of the puzzle with differet solutios, whether its load-balacig the Web servers hostig cotet for SharePoit s users or implemetig a redudat storage solutio to store SharePoit s data. Note: It s a well-kow fact that SharePoit puts the majority of its cotet ad data ito its back-ed SQL Server databases. Although this chapter does ot make direct metio of SQL Server HA (maily because Chapter 8, SQL Server 2008 High Availability covers this i depth specifically for SQL Server), the iformatio i the Storage sectio later i this chapter is still relevat for SQL Server hosts just as much as the servers that SharePoit is istalled o. The visual examples provided i this chapter were geerated i a testig eviromet usig the followig platforms ad compoets. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 Developer Editio with SP1 (build )

136 Chapter 6 Widows Server 2008 High Availability 119 Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 SharePoit. SharePoit Foudatio 2010 Release Cadidate 1 (build 4730) Load Balacig Oe of the best ways to esure that your SharePoit farm s cotet is always available to your users is by spreadig the resposibility for servig that cotet across multiple SharePoit servers via a practice kow as load balacig. Load balacig is most commoly applied to servers i a SharePoit eviromet that is assiged the Microsoft SharePoit Foudatio Web Applicatio role (i SharePoit 2007, these were ofte referred to as Web frot-ed [WFE] servers; you may otice that term used agai here for simplicity s sake), but SharePoit 2010 s ew Service Applicatio architecture itroduces a ew approach that allows other critical aspects of a SharePoit farm to be distributed across multiple poits of failure, such as Search or Busiess Coectivity Services. Iterestigly, the implemetatio ad cofiguratio of load balacig of these Service Applicatios are built ito the SharePoit product, but load balacig of the WFEs that deliver SharePoit to your users is ot. The ext two sectios address the is ad outs of cofigurig load balacig for your WFEs, followed by a examiatio of each server role that is available i SharePoit 2010 ad how (or if) they ca be made highly available. SharePoit is desiged to allow for the use of multiple WFEs i a load-balaced cofiguratio, servig up cotet to users o a sigle host ame. Eve though users may be makig complex requests to SharePoit, the servers are able to aswer those requests i a uiform maer, eve if durig a sigle sessio ed users are directed to multiple servers for their cotet. You ca loadbalace by istallig a hardware or software solutio i frot of your SharePoit WFE servers that forwards a Web request directed at a sigle host ame to oe of the WFE servers. If oe of the servers i your load-balaced pool is overwhelmed ad crashes, the load balacer ca redirect traffic away from the affected server to the other members of the pool, esurig a higher level of service cotiuity tha what is possible with a sigle server. Load-Balacig Software Load-balacig software is pretty easy to describe: by istallig ad cofigurig a applicatio o the SharePoit WFEs that you wat to load-balace, you ca distribute cliet requests across all those servers. It requires o special hardware ad usually comes with a lower price tag tha hardware-based solutios. I fact, the most commo load-balacig software solutio for SharePoit, Widows Network Load Balacig (NLB), is available as a Widows Server 2008 Feature, meaig it ca be added free of charge to ay server ruig Widows Server 2008, at ay time. This sectio guides you through eablig ad cofigurig a NLB cluster to load-balace the HTTP traffic directed at your SharePoit farm s WFE servers, as well as discusses the challeges of usig NLB with SharePoit. It is by o meas the oly way you ca use a software product to load-balace SharePoit, but it is the most prevalet optio available.

137 120 SharePoit 2010 Disaster Recovery Guide Cautio: Eve though NLB ad the Widows Server 2008 s failover clusterig (formerly kow as Microsoft Cluster Service or MSCS i Widows Serve 2003) feature share some of the same terms ad cocepts, they are two distict techologies iteded to provide solutios for differet problem sets. Failover clusterig is best suited for applicatios that require trasactios to occur i a sychroous order ad be aware of their positio withi that order, referred to as the applicatio s state. Applicatios that eed to frequetly update large amouts of data i a specific sequece, such as SQL Server, are excellet cadidates for clusterig via failover clusterig. NLB is targeted at applicatios that operate primarily i a stateless maer, such as IIS Web servers. The trasactios used by these applicatios geerally have o kowledge of the trasactios that came before or after them; each oe is treated as a idepedet operatio. Keep i mid that Share- Poit s Web traffic is t always stateless, i fact, it ofte is t, which is why some NLB settigs, such as affiity (discussed later i the chapter), are used differetly for SharePoit tha they may be for other Web-based applicatios. About Widows Network Load-Balacig Services Widows NLB is desiged to be a scalable, reliable, high-availability solutio for applicatios that commuicate via the Iteret Protocol (IP). It allows up to 32 servers to be placed ito a server farm cluster to avoid outages or performace losses for a sigle host ame. To cofigure a NLB cluster, a sigle host ame ad its IP address serve as a virtual IP that receives all traffic directed at the applicatio ad reroutes it to oe of the member servers withi the NLB cluster. If a member of the cluster fails, NLB automatically removes the server from the cluster ad distributes its load amog the rest of the servers i the cluster util service is restored o the affected server. NLB does ot require special hardware to cofigure or use its fuctioality. No hardware devices or storage area etwork (SAN) cofiguratios are required. For optimal use, the member servers i the NLB cluster should have two etwork iterface cards (NICs), but you ca certaily use NLB if the servers have oly oe NIC. Cofigure each member server to allow etwork commuicatio with the server via IP, because NLB relies o this protocol to commuicate with the cluster ad direct traffic through it. What s New i Widows Server 2008 ad Widows Server 2008 R2 Although Widows Server 2003 was usually the operatig system (OS) of choice for SharePoit 2007 deploymets, the 2010 release of the SharePoit platform rus oly o Widows Server 2008 or Widows Server 2008 R2. The 2008 release, as well as the R2 release, of the Widows Server OS brought with it several ehacemets ad ew features for NLB. It is importat to uderstad if the eviromet you re workig with i SharePoit 2010 is usig Widows Server 2008 or Widows Server 2008 R2, because there are importat differeces betwee what each OS ca ad caot do. The two sectios that follow summarize the chages made to NLB i both releases.

138 Chapter 6 Widows Server 2008 High Availability 121 NLB Ehacemets ad Additios i Widows Server The followig key compoets or fuctios have bee sigificatly updated or added to NLB s feature set by Microsoft with the release of the Widows Server 2008 OS: Networkig. NLB ow fully supports IPv6 for traffic betwee servers ad offers ehaced driver performace ad scalability through its support of the Network Driver Iterface Specificatio (NDIS) v6.1. Multiple etwork addresses. NLB ow supports the clusterig of multiple dedicated IP addresses per ode i the NLB cluster. WMI ehacemets. The MicrosoftNLB amespace withi Microsoft s Widows Maagemet Istrumetatio (WMI) has bee updated to support NLB s IPv6 ad multiple IP address ehacemets. Ehaced iteractio with Forefrot TMG. Whe used i cojuctio with Microsoft s Forefrot Threat Maagemet Gateway (TMG) 2010 Eterprise Editio, NLB offers better otificatio of potetial attacks ad maagemet of multiple IP addresses per ode. NLB Ehacemets ad Additios i Widows Server 2008 R2. With the release of the Widows Server 2008 R2 OS, Microsoft has updated its NLB solutio with eve more ew or improved features, icludig these: Improved affiity. NLB s affiity fuctioality (see the NLB Sessio Affiity ad Share- Poit sectio that follows for more iformatio o NLB Affiity) has bee updated to allow for relatioships betwee odes ad cliets to be held loger, eve if they are discoected. PowerShell support. The PowerShell scriptig laguage ow allows for the scriptig of NLB s cofiguratio ad maagemet activities. Flexible upgrades. Existig NLB clusters created o Widows Server 2003 ca be upgraded all at oce to Widows Server 2008, or member servers ca be upgraded oe at a time, a process kow as rollig upgrades. Health moitorig. Microsoft has released a NLB-specific maagemet pack for use with its eterprise moitorig product, System Ceter Operatios Maager (SCOM) NLB s Operatioal Modes You ca cofigure NLB to operate i two modes: Uicast ad Multicast. You must set all the member servers withi a NLB cluster to the same operatioal mode, regardless of whether Uicast or Multicast is selected. Uicast. I Uicast mode, the Media Access Cotrol (MAC) address assiged to the NIC for clustered traffic is overridde by a virtual MAC address that the NLB geerates. Each server i the cluster uses the same MAC, which meas that each member server receives all

139 122 SharePoit 2010 Disaster Recovery Guide traffic directed at the cluster. Uicast mode ca cause coflicts with etwork-switchig hardware, leadig to dropped traffic to ad from the cluster or to the switch beig flooded by traffic it ca t redirect. Multicast. I Multicast mode, a secod MAC address is added to the NIC of each member server i the cluster, ad the origial MAC address for the NIC is retaied. The NLBgeerated MAC address seds ad receives traffic directed at the NLB cluster s virtual IP address. The origial MAC address seds ad receives traffic directed specifically at the member server o its ow IP address. With Multicast mode, your etwork admiistrators ca create static etries i the cluster s etwork switch that poit to the ports used by the cluster, removig the risk of floodig your switch. Widows Server 2008 also itroduces a ew Multicast optio Iteret Group Maagemet Protocol (IGMP) multicast which eables IGMP support for limitig switch floodig by limitig the NLB cluster s traffic to oly those ports o the switch servig the cluster hosts ad ot all its ports. If you are usig IPv4 addresses i your etwork, you ca oly use Class D IP addresses (that is, addresses i the to rage) as your clustered IP address with the IGMP multicast cluster operatio mode. Although Uicast mode is eabled by default whe creatig a NLB cluster, Multicast mode is the operatig mode ofte recommeded for NLB clusters. Multicast mode provides more fuctioality whe oly a sigle NIC ca be used o member servers i the cluster; it avoids the issue of switch floodig as log as static etries are created i the switch to properly map the cluster s address to the ports beig used by the cluster. Uicast, o the other had, does ot fuctio well (some would say it does t fuctio at all) if your server has oly oe NIC, ad it causes switch floodig o matter what you do. If your etworkig hardware does ot allow for the creatio of static port etries, Uicast is the route you should take. But, if your etworkig hardware does allow it, ad most moder hardware is ow Multicast-compatible, Multicast is the way to go. Tip: Whe plaig how to cofigure your NLB cluster, make sure to cosult ad ivolve your orgaizatio s etwork admiistrators. Not oly ca they provide details o how your etwork is cofigured ad how that impacts your desig, but they ca also give you valuable recommedatios ad costraits based o their kowledge of the etwork that your SharePoit eviromet uses. Cautio: There has bee a dramatic icrease i the use of virtualized servers i IT eviromets i recet years, ad with good reaso; virtual machies (or VMs) offer a umber of compellig features, such as quick deploymet, optimizatio of physical resources, ad flexibility of maagemet. If you are implemetig NLB o VMs i your SharePoit eviromet ad pla to use Uicast mode as your cluster s operatioal mode, there are

140 Chapter 6 Widows Server 2008 High Availability 123 additioal cosideratios you eed to make for the cofiguratio of your virtual etwork resources, both NICs ad switches. VMware has published a excellet white paper ( that we recommed you review for more detailed iformatio o the subject ad how you eed to cofigure your virtual eviromet for NLB ad Uicast. How to Cofigure Widows NLB Services The followig istructios detail the steps ecessary to istall ad cofigure NLB to create a cluster cotaiig two physical servers. Each server has two NICs istalled, but the cluster is goig to be cofigured to operate i Multicast mode so that oly oe NIC o each server is used for the cluster. The user executig these steps must be a local admiistrator o each of the servers i the cluster. The member servers i the cluster have uique IP addresses assiged to each of their NICs, ad a IP address is available to serve as the cluster s virtual address. 1. Log o to the server you wat to add to a NLB cluster as a admiistrator. 2. Ope the Server Maager if it is ot already ope, ad click o the Features item i the left meu. The Network Load Balacig Feature should be eabled o the server, as show i Figure 6.1. If it is ot eabled, add the Network Load Balacig Feature to the server before cotiuig. 3. Click the Start butto ad avigate to All Programs, Admiistrative Tools, Network Load Balacig Maager. 4. This opes the Network Load Balacig Maager applicatio, as show i Figure From the Cluster meu, select the New optio to ope the New Cluster : Coect widow (see Figure 6.3) ad create a ew NLB cluster. 6. Whe the New Cluster : Coect widow opes, eter the IP address ad subet mask for the first host to be added to the cluster, ad click the Coect butto. The NLB Maager searches for the server based o the IP address etered, ad if foud displays the ames ad IP addresses of ay NICs o the target server that are available to be added to the ew cluster i the Iterfaces Available for Cofigurig a New Cluster list. Select the row for the NIC to be added to the cluster i the list, ad click the Next butto to cotiue. Figure 6.3 depicts the New Cluster : Coect widow after a host to be added to the cluster has bee located ad a NIC o the server has bee selected. Cautio: I a Multicast cofiguratio such as the oe this process describes, you should leave at least oe of a server s NICs out of the NLB cluster. This NIC is eeded to eable traffic to directly reach the server o its ow uique address; addig it to the cluster would ot permit the Multicast cofiguratio to fuctio properly.

141 124 SharePoit 2010 Disaster Recovery Guide Figure 6.1 eabled. The Widows Server 2008 Server Maager, with the Network Load Balacig Feature 7. Whe the New Cluster : Host Parameters widow opes (see Figure 6.4), if you wat to add additioal host IP addresses to the cluster, click the Add butto to ope the Add IP Address widow (show i Figure 6.5). I this widow, eter the required iformatio for the server s dedicated IP address, ad click the OK butto. You ca eter IP addresses i IPv4 format, or IPv6 format as log as your etwork is set up to use that implemetatio of the Iteret Protocol. (If it is ot set up for IPv6, this optio is disabled.) After eterig the dedicated IP address for the server, click the Next butto to cotiue. If you wat, you ca cotiue without addig additioal IP addresses. If you wat to have multiple hosts participatig i this cluster, though, you must add them i this dialog box. 8. The New Cluster : Cluster IP Addresses widow is ow opeed, as show i Figure 6.6. IP addresses added i this widow are the target addresses that cliet computers use to access your SharePoit sites that are the load-balaced betwee the hosts i the NLB cluster. The IP address you eter here is the shared address that you should direct your users to use to access your load-balaced SharePoit site; the cluster takes the

142 Chapter 6 Widows Server 2008 High Availability 125 Figure 6.2 The Network Load Balacig Maager. traffic to this IP address ad redirects it to idividual server odes withi the cluster. To add a IP address, click the Add butto to ope the Add IP Address widow (idetical to the Add IP Address widow show for Host IP Addresses i Figure 6.5). I this widow, eter the required iformatio for the clustered IP address, ad click the OK butto. The IP address etered must be a static IP address; NLB disables the Dyamic Host Cofiguratio Protocol (DHCP) settigs o each NIC it cofigures, which is why static IP addresses are required. You ca eter IP addresses i IPv4 format, or IPv6 format as log as your etwork is set up to use that implemetatio of the Iteret Protocol. (If it is ot set up for IPv6, this optio is disabled.) After eterig the IP address for the cluster, click the Next butto to cotiue. 9. The New Cluster : Cluster Parameters widow opes, as show i Figure 6.7, allowig you to cofigure the shared Uhostame for the ew cluster you are creatig ad select the cluster s operatio mode. Eter the host ame for the load-balaced host ame of your SharePoit sites i the Full Iteret Name text field; select the radio butto for the desired cluster operatio mode, which i this case is Multicast; ad the click the Next butto to cotiue. 10. The New Cluster : Port Rules widow is ow opeed, as show i Figure 6.8. By default, a sigle rule has already bee created to ecompass every TCP ad UDP port

143 126 SharePoit 2010 Disaster Recovery Guide Figure 6.3 The New Cluster : Coect widow. o the clustered IP address. If you wat to modify that rule, click the Edit butto to ope the Add/Edit Port Rule widow (show i Figure 6.9). I this widow, you ca apply the rule to the etire cluster or a sigle IP address if there are multiple i the cluster, chage the rage of ports icluded i the cluster for the IP address, select the Iteret Protocol that the cluster uses, set its Filterig Mode, set its Affiity, or disable the selected rage of ports for the cluster. To accept the defaults for the rule, click the Fiish butto to iitiate the cofiguratio of the cluster. Note: A NLB cluster s Affiity settig cofigures how sticky a sessio is betwee a cliet ad a host withi the cluster. If Noe is selected for a cluster s Affiity, each cliet sessio is directed by the load balacer to the ext available host i the cluster, regardless of whether the cliet previously was commuicatig with a specific host. Selectig Sigle sets a cliet to always be directed to the same host withi a give sessio, regardless of its traffic load. The Network optio directs requests from the same TCP/IP Class C address rage, such as cliets usig multiple proxy servers to access the cluster, to a specific host i the cluster. For more iformatio about NLB Affiity settigs ad SharePoit, see the Widows NLB ad SharePoit sectio later i this chapter.

144 Chapter 6 Widows Server 2008 High Availability 127 Figure 6.4 The New Cluster : Host Parameters widow. Figure 6.5 The Add IP Address widow.

145 128 SharePoit 2010 Disaster Recovery Guide Figure 6.6 The New Cluster : Cluster IP Addresses widow. 11. Whe the cluster cofiguratio operatio completes, the cluster is show i the Network Load Balacig Maager scree i the left widow pae uder the Network Load Balacig Clusters etry (see Figure 6.10). To add hosts to the cluster, right-click o the ew cluster s ame ad select the Host Properties optio from the meu. This opes the Host Properties widow for the cluster (see Figure 6.11), allowig you to complete step 7 to add subsequet hosts to the cluster. Cautio: As you add servers to the cluster, remember that you must assig each server a uique idetifier determiig its priority withi the cluster. Also, you ca cofigure affiity idividually for each host, givig you greater opportuities for both flexibility ad complexity withi the cluster. Widows NLB ad SharePoit Whe implemetig Widows NLB with SharePoit, you eed to keep i mid ad cosider two mai issues: operatioal mode ad sessio affiity. You ca cofigure each of these items i differet ways, ad your choices ca have a defiite impact o the fuctioality ad performace of your SharePoit eviromet.

146 Chapter 6 Widows Server 2008 High Availability 129 Figure 6.7 The New Cluster : Cluster Parameters widow. NLB Operatioal Mode ad SharePoit. You are most likely to decide betwee Uicast ad Multicast based o the cofiguratio of your eviromet s etworkig hardware. If your servers i the NLB cluster are cofigured with multiple NICs ad floodig your switches is ot a issue, Uicast is the best-fittig operatioal mode. If your servers have oly oe NIC or switch floodig impacts the performace of your etwork, Multicast makes the most sese. If you are buildig your servers from the groud up, the recommeded approach is to istall more tha oe NIC ad go with Uicast, but these recommedatios are based o geeral situatios, ad your specific requiremets ad eviromet may dictate otherwise. Regardless of the operatioal mode you select, make sure to apply this settig uiformly across all servers i the NLB cluster; each ode must use the same settig, or you ll ecouter errors. Note: If you use Multicast i your cluster, make sure that your etwork s hardware is compatible. Specifically, your hardware must be able to accept the Address Resolutio Protocol (ARP) replies geerated by the multicast odes i the NLB cluster or allow admiistrators to create a static ARP etry to properly resolve the addresses that the cluster is usig. Although most moder etworkig hardware is ow compatible with the fuctioality ad settigs required to make NLB work, you may still ecouter legacy or iche hardware that is ot compatible. You eed to cofirm that your ifrastructure meets the eeds of your solutio ad thoroughly test the full cofiguratio before usig it i a productio eviromet.

147 130 SharePoit 2010 Disaster Recovery Guide Figure 6.8 The New Cluster : Port Rules widow. NLB Sessio Affiity ad SharePoit. Iteret traffic, by desig, is iteded to be stateless. That is, each trasactio betwee a cliet ad a server is supposed to be self-cotaied ad ucoected so that it ca be routed by the most efficiet meas possible regardless of how commuicatio operated i the past. Some SharePoit sites, such as public-facig sites usig SharePoit s Web cotet maagemet fuctioality, are truly stateless, ad each host withi a NLB cluster should be set to Noe to take advatage of that stateless ature ad focus o usig the cluster to improve performace ad stability. But the reality of the situatio is that ot all traffic over a etwork, eve a big etwork like the Iteret, is stateless. Ad, although SharePoit is i may ways a typical stateless Iteret applicatio, this is ot always the case. Some fuctioality, such as workflows or IfoPath forms, is proe to errors i load-balaced SharePoit eviromets where cliets ca commuicate with ay WFE server at ay poit i time. To avoid these errors ad place a greater emphasis o data itegrity, each ode i your NLB cluster should have Affiity set at Sigle so a cliet s repeated traffic becomes sticky by beig directed back to the same WFE server for each trip. This esures cotiuity i these trasactios that do require the persistece of state for proper operatio.

148 Chapter 6 Widows Server 2008 High Availability 131 Figure 6.9 The Add/Edit Port Rule widow. Advatages of NLB ad SharePoit. The most obvious advatage of usig Widows NLB is cost. Because SharePoit requires the Widows Server operatig system, you already obtaied the right to use NLB whe you purchased your Widows Server liceses. NLB does ot require the additioal purchase of expesive, proprietary hardware to eable HA for servig up your SharePoit cotet. Widows NLB also allows admiistrators to maage the NLB cofiguratio by loggig ito your SharePoit servers, providig a cetral locatio for the admiistratio of your eviromet s critical platforms. Drawbacks of NLB ad SharePoit. Widows NLB is ot a sophisticated load-balacig solutio. It ca require specific or at times uusual etworkig hardware to fuctio effectively. Its etwork badwidth requiremets make it a poor choice for load balacig across diverse locatios for geographic redudacy. For a sigle NLB cluster to be spread across two dataceters, the coectio speed betwee those dataceters must have respose times of 500 millisecods or less, a capability that could be difficult over extremely log distaces ad i certai wide area etwork (WAN) situatios. (Your etwork must be capable of supportig a subet that ca spa across a WAN coectio.) Aother possible solutio for multiple sites is to create a separate

149 132 SharePoit 2010 Disaster Recovery Guide Figure 6.10 A cluster show i the NLB Maager applicatio s widow. NLB cluster i each locatio ad direct traffic to oe or the other via a Domai Name Services (DNS) roud robi solutio, but this approach does ot truly distribute traffic loads betwee the sites. Perhaps NLB s biggest drawback is its iability to detect whe a host withi a cluster is o loger servig live cotet. If the IIS Web server i oe of your SharePoit WFEs has crashed ad is o loger sedig Web pages to requestig cliets, the NLB cluster cotiues to direct traffic to the Web server util its service is restored or the host is maually removed from the cluster. This ca have a defiite impact o your eviromet, because some ed users are goig to see itermittet errors while that dowed server is still beig used by the cluster ad that ca be difficult to troubleshoot. It also requires maual itervetio by a admiistrator, ot oly to remove the affected server from the cluster, but to determie which server is displayig the errors i the first place. Differetiatig betwee load-balaced servers ca be difficult whe each is geeratig the same cotet, addig additioal challeges to your ability to provide stable ad cosistet service via NLB. Load-Balacig Hardware Hardware load balacers are specialized etworkig applicatios desiged to route traffic to certai idividual servers i a etwork. You ca cofigure hardware load balacers to distribute

150 Chapter 6 Widows Server 2008 High Availability 133 Figure 6.11 The Host Properties widow of a ewly created NLB cluster. etwork traffic across multiple servers based o a variety of coditios such as coectio volume, badwidth utilizatio, processor utilizatio, ad overall server performace. Software load balacers add a additioal task load to the servers i the cluster o top of their ormal tasks, such as geeratig the load-balaced cotet. Hardware load balacers, o the other had, are specialized hardware devices whose sole resposibility is distributig traffic to their costituet servers accordig to their cofiguratio. They are desiged, egieered, ad tested to efficietly ad flexibly spread etwork traffic across the servers clustered beeath them. The most obvious beefit to the use of a hardware load balacer is the reductio of workload o your servers compared to Widows NLB. Because the servers are ot resposible for establishig ad maagig the NLB cluster, those free cycles ca be allocated to other resposibilities, such as geeratig ad servig cotet. Hardware load balacers also offer a variety of cofiguratio ad maagemet optios, although optios do vary from maufacturer to maufacturer. Traffic destiatios ca be determied by affiity, server workload, badwidth availability, geographic locatio, ad several other factors. Clusters ca spa etwork subets or eve dataceters. Servers ca be automatically or maually removed from active service depedig o a rage of criteria such as failure to respod or errors beig displayed i requested cotet. Hardware load balacers are offered by several etwork hardware vedors, icludig Cisco, F5, Juiper, Coyote

151 134 SharePoit 2010 Disaster Recovery Guide Poit Systems, Barracuda Networks, ad may more. Each vedor has its ow feature sets, capabilities, ad limitatios. You should work with your orgaizatio s etwork admiistrator(s) to determie the hardware solutio that is the best fit for your eeds if you decide to use a hardware load balacer. Load-Balacig Hardware ad SharePoit Much like Widows NLB, hardware load-balacig is goig to be most effective for a Share- Poit farm whe its affiity settigs are cofigured to meet the farm s most prevalet usage patter, such as makig sessios sticky whe data eeds to be maitaied across server calls or stateless whe trasactios are aoymous. This is a uiversal requiremet that should be tested ad implemeted (whe testig shows that it is beeficial) wheever possible. Oe differece betwee hardware load balacers ad Widows NLB is that the Uicast/Multicast operatig modes are fuctios uique to NLB; there may be hardware solutios that offer similar fuctioality or drawbacks. You should review their documetatio ad coduct your ow testig to determie the behavior of that fuctioality. SharePoit is supported o most, if ot all, hardware load-balacig solutios, so it is ultimately up to you ad your etwork admiistrators to determie which solutio is right for you. Whe evaluatig a hardware load balacer, do ot make your choice simply based o the load-balacig fuctioality of the devices. Also cosider each cadidate s maageability ad flexibility, because etworkig admiistratio (especially for Web server-based solutios like SharePoit) is a fluid ad ever-chagig resposibility. Your hardware load balacer should be able to quickly eable cofiguratio chages, effectively idetify status chages i the servers beeath it, ad make your life as a SharePoit admiistrator easier, ot harder. As SharePoit s sales ad popularity have grow, so has the eed to deliver it to ed users efficietly ad cosistetly. This has ot goe uoticed by the maufacturers of hardware load balacers; several have begu to provide iformatio, guidace, ad cofiguratios specifically geared toward the load balacig of SharePoit cotet with their products. This is great ews for SharePoit admiistrators, because it meas that the maufacturers have take care of the extesive testig ad moitorig activities ecessary to fid the cofiguratio sweet spot for ruig SharePoit behid their devices. This allows you to quickly ad ofte drastically improve the performace of your SharePoit eviromet with reduced risk to your service quality. You should still exercise cautio whe cosiderig a hardware load-balacig device optimized for SharePoit, because the gais i stability ad fuctioality offered by these products ca vary drastically depedig o the cofiguratio of your SharePoit eviromet ad its etwork. If your SharePoit servers ad the cliet workstatios accessig your SharePoit site have highbadwidth coectios, you may ot see performace gais worth the cost of implemetig a SharePoit-optimized load balacer. This is because may maufacturers have focused o situatios where etwork cofiguratios lead to smaller or slower pipes for data to flow through,

152 Chapter 6 Widows Server 2008 High Availability 135 such as WAN coectios. Coectio speeds for WANs, which ofte use public commuicatio liks to coect local area etworks (LANs) across multiple geographic locatios, ca pale i compariso to LANs. It is easy to uderstad, give the coectio limitatios WANs face ad the amout of etwork traffic that a active SharePoit site ca geerate, why this is a mai area of focus for maufacturers. But if your etwork does ot use or iclude WAN coectios, you may ot see large performace gais whe usig a SharePoit-optimized load-balacig device. Does this mea you should t use such a device i your etwork? Not at all. It s just that you eed to evaluate the reasos ad requiremets for load-balacig devices, alog with the possible aveues of growth your etwork might follow, ad select your resources accordigly. If your eviromet is ot likely to iclude WAN coectios ad there is a more affordable device available that offers all the load-balacig capabilities you eed, it is probably a better choice tha a expesive purchase for techology that you are ot goig to see much beefit from. Advatages of Hardware Load Balacig ad SharePoit. Because hardware load balacers usually ru o computig devices specifically devoted to providig load-balacig capabilities to a etwork, they are geerally more stable ad reliable tha NLB. NLB has to ru o your SharePoit WFE servers, so it is usig computig resources that are tasked with a variety of fuctios. This i tur ca lead to cotetio ad impact the performace of a NLB cluster. But because hardware load balacers do ot face the same competitio for resources, they are more stable ad offer better performace. Hardware load balacers also offer a much wider rage of fuctioality ad features tha what s available i NLB. Depedig o what the maufacturer of a specific device decides to iclude i it, you may have optios for securig, compressig, or cachig traffic set through the device, ot preset i NLB. Also, hardware load balacers ofte ca better idetify ad respod to errors, such as routig traffic away from failed odes without a outage, or eablig a predetermied static error page should all of a cluster s odes become uavailable. Drawbacks of Hardware Load Balacig ad SharePoit. Just as cost is a advatage for NLB, the high cost of purchasig specialized hardware is a defiite drawback for hardware load balacig. The good ews is that this is a diverse marketplace with offerigs fillig a broad rage of price poits, ad feature sets to match those costs. For some budget-mided orgaizatios, it might be awfully difficult to get away from a compariso of potetially high costs agaist NLB s price tag of $0.00. Addig a hardware load balacer to your eviromet also meas that you eed to itegrate yet aother compoet from yet aother maufacturer ito your eviromet, addig to its overall complexity ad makig it more difficult to maage. Maufacturers ofte implemet uique, proprietary hardware compoets ad setups to add to their ability to differetiate their products ad lock customers ito their solutios. These depedecies ca make it more difficult to maage your SharePoit eviromet i geeral, ot to metio your HA solutios i particular.

153 136 SharePoit 2010 Disaster Recovery Guide Fially, ot all hardware load-balacig optios offer the advaced error detectio ad hadlig capabilities metioed earlier, which meas your eviromet could face the same kid of risks NLB clusters do because they lack this fuctioality. Regardless of the load-balacig solutio you choose, make certai that you uderstad exactly what it ca ad caot do; optimally, you ll be able to mitigate those risks via other tools or procedures, but at a miimum you eed to be aware of what they are. Load Balacig ad SharePoit Farm Topology Implemetig load balacig to distribute traffic across multiple resources withi your Share- Poit farm ca positively impact the performace of your servers ad, most importatly, the ed user experiece. It ca also esure that your eviromet ca withstad the loss of a server withi the farm by sharig the load betwee multiple resources. But you do t achieve that beefit simply by addig more servers to your eviromet, istallig SharePoit o them, ad addig them to a NLB cluster. You eed to uderstad ot oly the areas withi your Share- Poit farm where load balacig ca be advatageous, but where it provides little to o value ad where it ca actually be detrimetal to the health of your system. Not oly that, but Share- Poit 2010 itroduces a ew approach to scalability with the Service Applicatio model (which replaces the SharePoit 2007 cocept of Shared Service Providers, or SSPs); allowig you to architect a much more highly available solutio for your etire SharePoit eviromet, ot just your Web servers or SQL Server istaces. The WFE Role The most obvious item withi your farm that beefits from load balacig is the WFE role, which is resposible for servig SharePoit s Web pages, cotet, ad fuctioality to your ed users. If you have a large user base who frequetly visit your SharePoit sites or you eed to make sure that your cotet is always olie ad available, you will most certaily wat to load-balace your WFEs. Oe iterestig thig that Microsoft discovered i SharePoit 2007 about load-balacig WFE servers is that there is a poit where the performace of your eviromet flattes as you isert additioal WFEs to scale out the farm. Microsoft coducted extesive testig of how SharePoit 2007 performs uder extremely heavy loads, for a variety of typical use cases. Although Microsoft has made a great deal of iformatio about the product available well ahead of its release, the problem with SharePoit 2010 beig such a ew product is that there just has ot bee eough time to do the same kid of capacity performace testig with the fial versio of the product. To its credit, Microsoft has bee workig to deliver this cotet with the lauch of SharePoit 2010, but it is ot fully released for all of SharePoit s umerous use cases. At the time this book is beig writte, Microsoft has released case ad lab studies that examie the performace

154 Chapter 6 Widows Server 2008 High Availability 137 metrics of large-scale SharePoit eviromets focused o collaborative activities, SharePoit s most commo use. Much as i SharePoit 2007, these studies show that i a SharePoit 2010 collaborative eviromet, there is a defiitive poit where performace gais flatte out as ew WFEs are added to a load-balaced farm. The flatteig teds to occur whe a fourth WFE is added to a farm. After that poit, there was o value i addig additioal WFEs. Beyod the fourth WFE, performace was beig costraied by CPU utilizatio o the SQL Server istace hostig SharePoit s databases, ot SharePoit itself. If you would like more iformatio o Microsoft s testig approach ad fidigs with SharePoit 2010 s capacity ad performace limitatios, head to the Capacity Maagemet for SharePoit Server 2010 Resource Ceter o TechNet, at It is a outstadig repository that is sure to have ew cotet o the subject of SharePoit 2010 capacity plaig added o a regular basis ad well worth a look. If you are plaig a large implemetatio of SharePoit, test your cofiguratio o its ow so that you ca determie your performace baselie ad whether it s goig to meet your eeds. Performace may vary depedig o a variety of factors, as follows: Network cofiguratio. The uique cofiguratio of your etwork ad its hardware may provide you with performace metrics that vastly differ from Microsoft s. Hardware cofiguratio. The uique cofiguratio of your server hardware may also provide you with performace metrics that vastly differ from Microsoft s. Cachig cofiguratio. Cofigurig your farm s servers ad cotet to leverage cachig fuctioality ca drastically improve the performace of your Web servers. Farm usage scearios. A farm iteded for iteral collaboratio ad kowledge sharig by autheticated users is goig to perform differetly from a farm iteded for Web cotet maagemet ad aoymous users. Addig More Servers to a SharePoit Farm Because load balacig is commo for SharePoit to improve performace, Microsoft has made the process to add additioal servers to a SharePoit farm easy ad straightforward. The SharePoit istaller should be ru o the server to be added to the farm, usig the same accouts ad cofiguratio as the rest of the servers i the farm, makig sure to do a Complete Advaced istallatio. Oce the istaller fiishes, the SharePoit Products ad Techologies Cofiguratio Wizard starts up. Walk through the wizard, makig sure to select the Coect to a Existig Farm optio, ad the coect to the cofiguratio database for the existig farm. Cofirm that the server is ot set to host the farm s Cetral Admiistratio site (uless you have a specific requiremet to create a redudat site), ad complete the wizard. Log ito the Cetral Admiistratio site, ad cofigure the server with the WFE role that it should play i the farm.

155 138 SharePoit 2010 Disaster Recovery Guide Note: Addig a server to a farm withi SharePoit does ot automatically add it to the pool of load-balaced servers for Widows NLB. You must still perform this cofiguratio step i the maagemet tools for the load-balaced cluster, ot i SharePoit, for ed users to reach the server via the load-balaced URL. Service Applicatios I Microsoft Office SharePoit Server (MOSS) 2007, Microsoft itroduced the cocept of SSPs, applicatios withi a farm desiged to provide specialized services such as My Sites, Search, ad User Profiles to multiple Web applicatios withi the farm. SSPs were helpful i that they allowed commo fuctioality to be used cosistetly across sites ad Web applicatios i the farm, but the approach was ot without its drawbacks. SSPs were ofte difficult to maage, especially i large farms, ad they were a challege to protect from a DR stadpoit. I the case of Search specifically, SSPs represeted a sigle poit of failure because oly a sigle server could be desigated for operatio i the Idex Server role for a give SharePoit Search idex. Microsoft has revamped its approach to these types of applicatios i SharePoit 2010 by retirig the cocept of a SSP ad itroducig the Service Applicatio model. It also applies to both SharePoit Foudatio 2010 ad SharePoit Server 2010 istead of just the server product. Microsoft has desiged the Service Applicatio model to build o the directio take by the SSP approach while addressig some of its shortcomig ad drawbacks. Service Applicatios are desiged to provide scalability to your SharePoit farm, give admiistrators greater cotrol over which services are delivered to SharePoit resources, ad allow third-party vedors to create their ow custom Service Applicatios to ehace ad exted the fuctioality available through a SharePoit eviromet. The big reaso that Microsoft s chage from SharePoit 2007 s SSP model to SharePoit 2010 s Service Applicatio model makes such a differece is i how it hadles load. With SharePoit 2007, applicatios withi the SSP were ofte difficult to scale out as usage icreased. Some applicatios, such as Excel Services, required careful cosideratio ad cofiguratio to set up for large eviromets or high availability. Search i SharePoit 2007 was a eve more frustratig story: the Idex server role could ot be spread across multiple servers, makig it a sigle poit of failure. I a multiserver SharePoit 2010 farm, Microsoft recommeds that Service Applicatios are hosted o dedicated applicatio servers (givig the farm a three-tier hierarchy, with the other tiers cosistig of WFEs ad SQL Server hosts). These applicatio servers host the Service Applicatios ad respod to requests made by the cliet applicatios hosted by the farm s WFEs to deliver their fuctioality. If the farm has multiple applicatio servers, it is ot ecessary to cofigure a load-balaced cluster (via NLB or a hardware load balacer) as it would be for a farm with multiple WFEs. Istead, Microsoft has built a simple roud-robi load balacer ito its Service Applicatio Framework that distributes traffic across each applicatio server automatically.

156 Chapter 6 Widows Server 2008 High Availability 139 Search Roles The oe piece of SharePoit most impacted by the ew Service Applicatio model i SharePoit Server 2010 is Search. SharePoit s Search capabilities have always bee a highly touted aspect of the platform, ad that s o differet i 2010, featurig lots of ew features ad fuctioality for ed users. But with this ew release also comes a much better story aroud the idea of makig SharePoit s Search ifrastructure pieces highly available. This simply was t possible i MOSS 2007 due to the iflexible ature of the Idex server role, but SharePoit Server 2010 gives you a great deal of flexibility ad scalability. Note: The cotet i this sectio focuses almost etirely o the Search fuctioality of SharePoit Server Although SharePoit Foudatio 2010 does ow allow for the presece of multiple Search servers withi a farm, those servers caot be deployed redudatly. Each Search server must be cofigured to crawl ad idex differet cotet databases withi the farm, so you caot cofigure the farm so that if oe Search server goes dow its load is distributed to the other servers. If oe Search server goes dow, its idexed cotet is uavailable. There are also three other search products related to or for SharePoit 2010 from Microsoft: Search Server Express 2010, Search Server 2010, ad FAST Search Server 2010 for SharePoit. These products may be worth your cosideratio, but this book focuses o coverig ad protectig SharePoit s core fuctioality. Please review the documetatio for the products metioed to determie if ad how they ca be made highly available. SharePoit servers i a farm ca serve a few differet roles to add performace ad fuctioality to the farm s search capabilities. The two listed server roles affiliated with searchig i a Share- Poit farm are the Crawl server role (kow as the Idex server i MOSS 2007) ad the Query server role. Crawl servers are resposible for geeratig the farm s search idex by crawlig the target cotet sources ad buildig the idex with the results of that crawl. Query servers are tasked with the processig required to execute all requested queries agaist a copy of the farm s search idex stored locally o the Query server. I SharePoit 2010, you ca assig both the Crawl server ad Query server roles to multiple servers withi a farm, allowig for redudacy ad load distributio of SharePoit s Search fuctioality. A Crawl server must be associated with a sigle Crawl database; this database specifies the cotet that the Crawl server must crawl to build its assiged idex. This relatioship allows for Search idexig to be costructed for both redudacy ad scalability, as desired. You ca add redudacy to a farm s Search crawls by associatig multiple Crawl servers with a sigle Crawl database so that if oe Crawl server becomes uavailable, a replacemet is available to cotiue idexig the Crawl database s desigated cotet. If you wat to improve the performace of the crawl activities, you ca create additioal crawl databases. This allows you to separate the crawl cotet betwee databases so that multiple Crawl servers ca process ad crawl it i parallel.

157 140 SharePoit 2010 Disaster Recovery Guide Query servers respod to search queries submitted by ed users o WFE servers ad retur results usig the Search idex geerated by the farm s Crawl servers. If a sigle server i the farm is cofigured with the Query role, a copy of the etire idex is stored i the Query server s file system. If a farm has multiple Query servers, each Query server receives a idex partitio, or a portio of the overall idex. By default, the distributio of idex partitios is based o the umber of Query servers i a farm, but admiistrators ca maually specify the umber of idex partitios that are created ad how they are distributed. I the case of two Query servers, for example, each server stores a idex partitio equal to half the idex. If there are four Query servers, each server stores a idex partitio cotaiig 25 percet of the overall idex. This approach allows for redudacy (if oe of may Query servers i a farm goes dow, the idex partitios ca be redistributed to cover the outage) ad may improve performace as additioal Query servers are added to a farm. Cautio: Although the ew Search architecture i SharePoit Server 2010 overcomes a umber of the problems admiistrators faced with redudacy ad scalability i MOSS 2007, it still has compoets that you ca t duplicate withi a farm. Each farm requires a Search Admiistratio compoet that ca oly be deployed to oe Crawl server i a farm, ad oly oe Search Admiistratio database ca be associated with that sigle Search Admiistratio compoet. The database ca oly be made redudat if database mirrorig or clusterig is implemeted (see Chapter 8, SQL Server 2008 High Availability for more iformatio); the Search Admiistratio compoet itself caot be made redudat. The impact of losig these pieces would be miimal ad maily affect a admiistrator s ability to maage the Search fuctioality; the farm s Search service would still be available but could ot be modified. This ew Search architecture also allows for etire SharePoit Server 2010 farms dedicated to crawlig cotet ad respodig to search queries. This is typically oly a cosideratio i large, ofte global, SharePoit deploymets, but it does add versatility i search scearios that were ofte troublesome i MOSS High Availability Load balacig your Web servers is by far the most obvious ad effective way to esure cotiuous uptime for your SharePoit eviromet, but it does ot ecessarily represet a complete HA solutio. Because SharePoit requires such a wide rage of ifrastructure ad systems to fuctio, you eed to cofigure these systems redudatly so they ca be as highly available as your load-balaced SharePoit compoets. The failure of a hard drive or etwork coectio ca just as easily impact SharePoit s service levels as the more obvious cadidates for HA, SharePoit, ad SQL Server. Luckily, the IT idustry has bee hard at work for years to develop ad create stable, redudat ifrastructure compoets that address those problems.

158 Chapter 6 Widows Server 2008 High Availability 141 Storage Let s face it: it s impossible to have a server ruig Widows Server 2008 ad ot have some sort of storage device attached to it. Hard disk drives, commoly kow as hard drives, have bee used i computers for more tha 50 years ad have evolved ad improved as much as processors have over the years, albeit with much less fafare. Moder hard drives are desiged ot oly to store large amouts of data (maufacturers are ow producig drives with capacities measured i terabytes), but to make readig, writig, ad trasmissio of that data happe as quickly as possible. But oe thig has t chaged: drives still fail. That is ot to say that maufacturers have igored the reliability of their products. That statemet could ot be further from the truth. Today s hard drives are made to last loger while still withstadig the heavier workloads that itercoected, data-drive computer systems place upo them. They are beig made to use less power ad reduce oise ad to hadle sudde movemets such as those that could impact the hard drive of a laptop computer. But real-world experiece has show that hard drives are still proe to failure for a variety of reasos. To expect otherwise is foolhardy, if ot irresposible. Wat proof? Cosider the fidigs offered by Google, probably oe of the largest cosumers of hard drives i the world. I a white paper published i February 2007 ( Google preseted data based o aalysis of hudreds of thousads of hard drives. It foud that, despite the best efforts of maufacturers ad system admiistrators, hard drives are proe to failures caused by a variety of sources, especially as the drives become older. Age is ot the oly reaso for hard drive breakdow, ad Google is careful to poit out that it should ot be the oly determiig factor. But it s importat to keep i mid that as a drive gets older, it is more likely to fail. Whe it comes to the busiess-critical data stored o your servers ad i your SharePoit eviromet, we recommed that as a part of a effective disaster recovery pla, you should ot oly back up your data o a regular basis, you should also cofigure the systems you store that data o as redudatly as possible. This helps to make certai that your data is still available if a hard drive fails, ad it avoids ay outages that may be experieced while a backup is beig retrieved from storage ad restored. The good ews is that moder IT systems have some effective solutios available to them to redudatly store their data. RAID A Redudat Array of Idepedet (or Iexpesive) Disks, more commoly kow as a RAID array, is a storage solutio that uses two or more actual hard drives to create a reliable storage optio for servers. The multiple disks i a RAID array are cofigured to be preseted to a server as a sigle device, providig a redudat solutio that ca either copy or distribute data across the disks i the array. Note: Because there are so may hardware vedors ad cofiguratios for RAID arrays o the market today, be sure to review ay documeted performace metrics for your RAID

159 142 SharePoit 2010 Disaster Recovery Guide solutio, ad if possible do your ow testig, to better uderstad how quickly it ca do the various types of disk operatios you pla to use it for. As show ext, i geeral, differet RAID cofiguratios work best for differet types of operatios, but techological ad desig advaces may prove differetly for specific products. There are several types of RAID arrays, each providig differet attributes ad drawbacks to be cosidered. Some of the most commo are listed here: RAID 0. With RAID 0, data is striped, or broke dow ito blocks, ad each block is writte to differet disks i the array. RAID 0 requires at least two hard disks to implemet, ad its primary advatage is its ability to read ad write data to the disk much more quickly tha a sigle disk. Because data is ot duplicated across multiple disks i the array, RAID 0 does ot provide fault tolerace for high availability. RAID 1. I this cofiguratio, data is mirrored across each disk i the array so that it is preserved if a drive i the array fails. Writig to the array takes slightly loger tha a sigle disk, because the array is writig to multiple drives (a problem more ofte see i softwarebased RAID solutios tha i hardware-based oes). The available storage i the array is also limited to the size of the smallest disk i the array. RAID 5. This combies a miimum of three disks ad esures that the data o oe disk i the array is duplicated o at least oe of the other disks i the array. It provides fault tolerace (it ca withstad the loss of oe disk i the array), ad readig data from a RAID 5 is similar i performace to a RAID 0. Writig to a RAID 5 array is a differet story, because it geerally takes cosiderably more time to determie what should be writte ad where it should be writte withi the array. The total storage capacity of a RAID 5 array is the sum of all disks i the array but oe. RAID 6. This is similar i cofiguratio to RAID 5, but it offers additioal fault tolerace, allowig the array to survive the loss of two disks i the array. Read performace is equal to that of RAID 5, but writes ca take eve loger. The total storage capacity of a RAID 6 array is the sum of all disks i the array but two. RAID 10 (also kow as RAID 1þ0). RAID 10 is a combiatio of RAID 1 ad RAID 0. With RAID 1þ0, drives i the array are paired, data is mirrored across the pairs, ad the data is striped throughout the array. RAID 1þ0 ca also experiece the loss of up to 50 percet of the drives i the array ad still maitai data itegrity. RAID 1þ0 offers faster read ad write operatios tha RAID 5. Beyod the cofiguratio of the RAID array, there are two ways to implemet a array: software ad hardware. Software RAID. Some operatig systems, icludig Widows Server 2008, ca create RAID arrays by creatig logical disks that are the mapped to the physical disks attached to the

160 Chapter 6 Widows Server 2008 High Availability 143 server. Usig a software RAID cofiguratio ca reduce costs, but maagig the array ca impact a server s performace particularly i the case of computatioally expesive RAID cofiguratios, such as RAID 5. More importatly, maual itervetio is required to fail over the array if there is a hard disk failure withi the array, leadig to service outages. Hardware RAID. Hardware RAID cotrollers are specifically built to maage ad operate RAID arrays ad ca be implemeted as expasio cards istalled i the server or built ito the server s motherboard. They offer umerous advatages over software solutios, such as o use of a server s processig power, oboard cachig, better failover optios, ad better error hadlig, but they ca be expesive. It s difficult to advocate a specific RAID array cofiguratio for your SharePoit farm, because everyoe s requiremets, budget, ad ifrastructure are uique, ad these factors ifluece the decisio. Because server roles withi a farm use their hard drives i various ways, you may ed up with differet RAID array cofiguratios withi your farm. If your orgaizatio has a stadard cofiguratio for RAID arrays i its dataceters, review those settigs to cofirm that they meet your requiremets. The list that follows outlies several items you should keep i mid whe desigig your RAID cofiguratios. Use hardware RAID cotrollers whe possible. Hardware RAID cotrollers offer so may advatages over software-based cotrollers, especially where RAID is beig used to esure fault tolerace i disaster recovery solutios. They are more expesive to implemet, but they may prove to be worth the ivestmet if they ed up savig you big bucks by avoidig productivity-killig dowtime for your SharePoit eviromet. Right-size solutios for WFEs. WFEs do ot ecessarily eed big-time RAID 1þ0 arrays to store their data. I most situatios, RAID 1 or RAID 5 is sufficiet to provide data preservatio ad fault tolerace i case of a failure, because SharePoit WFEs do ot read or write as much data from ad to their disks as SQL Server 2008 does. Right-size solutios for SQL Server As you will see i Chapter 7, SQL Server 2008 Backup ad Restore, SharePoit s SQL Server databases mea everythig to the farm s survival. Moreover, SharePoit is pretty hard o its databases, performig coutless reads, writes, ad deletes to them every secod uder load. It makes sese to use the most faulttolerat, high-performig array cofiguratio you ca afford for the hard drives of your SQL Server. Use quality hard drives. A easy way to esure good performace for your RAID arrays is to use hard drives with fast access times ad large amouts of cache memory built i. Use eough hard drives. Addig disks to your arrays is aother easy way to improve RAID performace. This gives the array aother drive to store cotet o, provides additioal redudacy withi the array, ad ca icrease the available disk space (depedig o the array cofiguratio).

161 144 SharePoit 2010 Disaster Recovery Guide SAN The other storage optio available (besides just usig hard drives i your servers) that makes sese to use with SharePoit is storage area etworks, or SANs. SANs let you attach remotely located storage to a server so that the operatig system displays ad treats the storage as if it were local. SANs are usually best suited to large eterprises due to their high costs to implemet, but smaller orgaizatios ca also purchase maaged SAN storage products from hostig providers if desired. SANs ca be a viable disaster recovery solutio based o their ability to make storage resources available to servers i multiple locatios. SANs are also a good way to make large amouts of storage available i a cofigurable fashio; this makes them appealig as a storage locatio for SharePoit s SQL Server databases. As Chapter 8 explais, SAN storage is also required to eable Widows failover clusterig, a tool that ca be importat i makig SQL Server 2008 highly available. Although SharePoit s SQL Server databases defiitely led themselves to beig stored i a SAN, most of SharePoit s additioal storage eeds do ot map particularly well to a SAN solutio. I most cases, the beefits of a SAN are outweighed by the high cost of usig such a resource for the relatively small-i-compariso hard drives of a SharePoit server, especially whe there are other ways that the data stored there ca be backed up or made highly available. Widows Server 2008 ad Server 2008 R2 Storage Improvemets I additio to some of the hardware cosideratios for storage that you eed to be aware of, keep i mid that the server operatig system that you ru SharePoit 2010 o may also be able to do some ew thigs to help make your systems more highly available. Widows Server 2008 ow offers several features ot foud i Widows Server 2003 that ca help keep your server s storage healthy ad fuctioig properly, such as these: Self-healig NTFS. Prior to Widows Server 2008, if a Microsoft server OS detected corruptio i the file system of a New Techology File System (NTFS) storage volume (the most commoly used format for drives attached to computers ruig Microsoft operatig systems), the volume had to be take offlie to correct the errors that had bee foud. With Widows Server 2008, the operatig system is able to ru a process i the backgroud to repair ad isolate damaged regios without takig the full storage volume offlie. S.M.A.R.T error detectio. The Self-Moitorig, Aalysis, ad Reportig Techology (S.M.A.R.T.) moitorig system for computer disks has bee aroud for a while i moitorig systems like Microsoft System Ceter Operatios Maager 2007 (SCOM), but Widows Server 2008 is the first time that S.M.A.R.T. detectio techiques are beig used withi a Microsoft server OS to idetify ad war admiistrators of drive failures before they may arise.

162 Chapter 6 Widows Server 2008 High Availability 145 Ehaced maagemet of storage etworks. Microsoft implemeted the Iteret Storage Namig Server (isns) protocol i Widows Server 2008, which allows the OS to maage disks attached via the Iteret Small Computer System Iterface (iscsi) just as it would disks attached to the server via Fibre Chael (such as SANs). This makes maagemet of those iscsi devices much simpler ad more effective. Disk resizig o the fly. With Widows Server 2008, admiistrators ca ow resize hard disk partitios without shuttig dow the server hostig the partitios, eve if the target partitio is the system drive. Although this does ot apply to striped drives (such as drives cofigured i a RAID-0 array), it does allow for greater flexibility whe maagig your servers storage. I October 2009, Microsoft made available a secod release of Widows Server 2008, kow as Widows Server 2008 R2. (Microsoft is clever with its amig stadards for this product, is t it?) This updated release cotaied a wide rage of ew features ad fuctioality for Microsoft s flagship server operatio system, but ot eough to warrat icremetig the product s versio umber. The R2 release had two updates that were pertiet to server storage: Storage fault tolerace. If a server ruig o Widows Server 2008 R2 has multiple paths coectig it to a storage device, the OS ca switch to a alterate path to the device should the primary fail or become uavailable. The OS also allows for the cofiguratio of the priorities for these paths to your storage device for better flexibility i cofiguratio. Storage cofiguratio backups. Widows Server 2008 R2 allows admiistrators to take sapshots of their storage cofiguratio settigs, such as its iscsi setup, so that the server ca be quickly restored to a fuctioig state should the cofiguratio fail or chage uexpectedly ad affect the availability of a server s storage. Server Clusterig ad SharePoit The most commo elemet of SharePoit to make highly available via a clusterig tool such as Widows failover clusterig is its SQL Server databases. The topic of Widows failover clusterig ad SQL Server is covered extesively i Chapter 8. Networkig ad Ifrastructure Plaig The other elemet of your SharePoit eviromet that is vulerable to hardware failures ad outages is your etworkig hardware ad ifrastructure. If your etwork or a compoet withi it should fail, is your eviromet redudat eough to keep lies of commuicatio ope betwee your users ad your SharePoit farm? What about betwee your SharePoit farm ad its database servers, domai cotrollers, ad other crucial remote resources? Do t overlook the vital compoets that provide the key lies of commuicatio ito ad out of your eviromet whe plaig for high availability.

163 146 SharePoit 2010 Disaster Recovery Guide Work with your etwork admiistrator(s) to cofirm that the switches, routers, load balacers, ad other pieces of the etwork are redudat, so that the coectio to the etwork remais active if oe of those items should fail. Regularly test your etwork to cofirm that commuicatios are beig quickly ad efficietly routed from poit A to poit B, ad to make sure that all address mappigs ad cofiguratios are correct so that traffic ca get to where it is supposed to. Your servers ca be cofigured with additioal NICs, a setup that ca offer a lot of additioal beefit to your system. Not oly do multiple NICs allow for the use of the Uicast operatig mode with Widows NLB, but you ca establish specific chaels for commuicatio, restricted to a specific IP subet, betwee your SharePoit servers ad their database istaces. This is beeficial to performace, because it gives your farm a etwork locatio solely devoted to its ow database traffic, the foudatio of SharePoit s publishig process. It also provides importat security to the process by restrictig access to the IP subet to oly the servers usig it. Multiple NICs ca also be teamed, opeig up greater badwidth ito ad out of your server for cotet to flow through, as well as makig it possible to add greater redudacy ad failover capabilities to your servers should a NIC fail. Coclusio As a SharePoit admiistrator, it is all too easy to become locked oto the SharePoit or SQL Server compoets of your eviromet. But from the perspective of disaster recovery ad high availability, that just is t eough. SharePoit depeds o may systems, devices, ad processes to fuctio effectively. As a admiistrator, it is your resposibility to make sure that those costituet items are just as robust, redudat, ad available as your SharePoit systems are. How you are able to accomplish that depeds a lot o the kid of operatig budget you have available ad your existig resources. The good ews is that SharePoit ad its costituet systems are pretty flexible, so you have flexibility ad optios. Oftetimes, the hard part is siftig through those optios to determie which is best for you. A poit that we have cosistetly stressed throughout this book is the importace of testig ad moitorig everythig withi your eviromet. It is far better to kow ahead of time whe a system is failig or eeds repair or modificatio, because that way you have more time to pla the right solutio ad put it i place ot to metio that it s a much easier coversatio to have with your supervisor ad customers tha the alterative. The cocepts ad iformatio i this chapter are desiged to get you thikig about the foudatioal systems of your SharePoit eviromet ad what you ca do to make them highly available. The best solutio for you depeds o your orgaizatio ad its eeds, but whether you have a sigle SharePoit Foudatio 2010 server that is accessed by 10 users or a global orgaizatio with multiple SharePoit Server 2010 farms ad thousads of users, implemetig some, ay, or all of the cocepts i this chapter ca oly beefit your SharePoit eviromet. After completig this chapter o Widows Server 2008 High Availability, you should be able to aswer the followig questios about their capabilities. You ca fid the aswers to these

164 Chapter 6 Widows Server 2008 High Availability 147 questios i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at 1. Do you eed to purchase a separate licese for Widows NLB? 2. What is the differece betwee Uicast ad Multicast operatig roles for NLB? 3. What SharePoit server roles ca be load-balaced? 4. How does RAID 1þ0 differ from RAID 5? 5. What ew storage maagemet features were itroduced i Widows Server 2008 R2?

165 This page itetioally left blak

166 7 SQL Server 2008 Backup ad Restore I This Chapter SharePoit s Database Optios How to Back Up a SQL Server 2008 Database SharePoit ad Backig Up SQL Server 2008 How to Restore a SQL Server 2008 Database Backup SharePoit ad Restorig a SQL Server 2008 Backup It seems these days that the majority of applicatios, whether they are used by the largest of corporatios or the average Joe User, rely heavily o back-ed databases to retai the iformatio associated with the applicatios. Tools such as Oracle PeopleSoft ad Microsoft BizTalk, as well as Web sites such as Amazo.com, Salesforce.com, ad Microsoft.com, store large quatities of data i databases that they could ot fuctio without. I SharePoit, you have yet aother excellet example of a applicatio platform built o top of back-ed databases, usig those databases to store cotet, user profile data, cofiguratio settigs, ad much more. But SharePoit is also somewhat uique i how much it depeds o its back-ed databases. A overwhelmig majority of the data ad settigs associated with SharePoit are actually stored i SharePoit s databases, ot the file system of the SharePoit servers i a farm. It ca be quite a surprise to a first-time SharePoit admiistrator to lear that the documets i a library are actually stored i SharePoit s back-ed database; this is ot a fact easily explaied or grasped util you really start to examie the platform. I fact, by default SharePoit does ot save cotet o a server s file system. It iserts all cotet ito a SharePoit cotet database i SQL Server ad retrieves it as requested to be displayed to the user i a Web browser. Wheever SharePoit loads a page for a user, it makes calls to its databases to determie what goes o the page ad how it is displayed. Grated, SharePoit also uses the template files ad applicatio code stored o its servers whe rederig a page, but it s a good bet that if you have uique cotet o a SharePoit site, it s beig retrieved from a database. 149

167 150 SharePoit 2010 Disaster Recovery Guide The same goes for the cofiguratio settigs ad details for your SharePoit eviromet. The majority of such iformatio is ot saved i a cofiguratio file or the Widows Registry o your SharePoit servers. Istead, SharePoit has a specific cofiguratio database desiged to house the cofiguratio settigs for your eviromet as well as details o every server ad Web applicatio i it. Sayig that SharePoit is somewhat depedet o its databases to operate is like sayig that you somewhat eed oxyge to live; if SharePoit s databases go dow, it caot display documets, cotet, or eve the simplest of pages without a error message. That meas if you wat your SharePoit eviromet to be up ad ruig 24 hours a day, 7 days a week, 365 days a year, you had better take a close look at your SQL Server istallatio ad how to keep it up ad ruig, because if it goes dow, it makes o differece what SharePoit s status is. Iitially i this chapter, we cover the basics of how to back up ad restore your SQL Server databases. Oce we ve set the stage with the uts ad bolts of SQL Server backup ad restore, we ll dive ito the specifics of how you ca, should, ad should ot protect your SharePoit databases usig SQL Server s built-i tools. Be wared: this chapter is iteded to outlie the mechaics of how to cofigure Microsoft SQL Server to support SharePoit i the evet of a catastrophic occurrece. It does ot go ito great detail about the architecture ad admiistratio of Microsoft SQL Server for geeral, o-sharepoit catastrophic operatios. We ecourage you to discuss ad review the cocepts ad practices i this chapter with your database architects or admiistrators (DBAs) so they ca be itegrated with ay disaster recovery activities that those parties may already have i place or are plaig for your database servers. If you are also directly resposible for the admiistratio of the SQL Server eviromet used by your SharePoit farm, you may wat to cosider obtaiig a additioal resource o SQL Server disaster recovery to further supplemet the iformatio i this chapter. SharePoit s Database Optios As you have hopefully already ecoutered by this poit i your jourey with SharePoit, SQL Server i some shape or form is required to successfully istall the SharePoit platform. Both SharePoit Foudatio 2010 ad SharePoit Server 2010 ca ru with several variatios of SQL Server as their back-ed database but caot use other o-sql server database platforms such as Oracle, MySQL, or eve Microsoft s Access i that role. This requiremet ca be frustratig ad limitig if your orgaizatio favors a database platform other tha SQL Server, but it is ot somethig that ca be worked aroud or hacked to use a differet type of database. If you implemet SharePoit, you are also goig to be istallig some icaratio of SQL Server; it is just that simple. As absolute as that costrait is, you are ot without some optios i exactly what flavor of SQL Server you choose to use as your SharePoit database provider. The list that follows outlies the six most commo SQL Server variats that ca host SharePoit 2010 s back-ed databases: SQL Server Microsoft supports SharePoit 2010 o the 64-bit versio of SQL Server 2005 SP3 with Cumulative Update (CU) package 3. Ay available editio of SQL Server 2005

168 Chapter 7 SQL Server 2008 Backup ad Restore 151 (Developer, Workgroup, Stadard, ad Eterprise) is supported with SharePoit, subject to the editio s limitatios (for example, the Developer SKU caot be used i a productio eviromet), as log as it is 64 bit. Although it is t the latest ad greatest database product available, SQL Server 2005 provides a stable database platform for SharePoit, aalysis services, graphical ad commad lie maagemet tools, ad much more. SQL Server 2005 Express. Much like the Microsoft SQL Server Desktop Egie (MSDE), SQL Server 2005 Express is a free editio of SQL Server 2005 distributed by Microsoft for use i small applicatios or eviromets. Express is costraied by three major limitatios: the size of its databases (limited to 4GB of storage), its ability to use oly a sigle CPU, ad its ability to address oly up to 1GB of RAM. Express ca be maaged via a available graphical maagemet tool or the commad lie. SQL Server 2005 Express should be patched to the same versio as SQL Server 2005 s full editios, SP3 with CU3. SQL Server Microsoft supports SharePoit 2010 o the 64-bit versio of SQL Server 2008 SP1 with CU2, CU5, or ay CU greater tha CU5 applied. Ay available editio of SQL Server 2008 (Developer, Workgroup, Stadard, ad Eterprise) is supported with SharePoit, subject to the editio s limitatios, as log as it is 64 bit. SQL Server 2008 is the latest full release of Microsoft s eterprise database platform, offerig several fuctioal improvemets over SQL Server 2005, such as improved performace, spatial data types, backup compressio, ad much more. SQL Server 2008 Express. SQL Server 2008 Express is a free editio of SQL Server 2008 distributed by Microsoft for use i small applicatios or eviromets. Express is costraied by three major limitatios: the size of its databases (limited to 4GB of storage), its ability to use oly a sigle CPU, ad its ability to oly address up to 1GB of RAM. Express ca be maaged via a available graphical maagemet tool or the commad lie. If you choose the all-i-oe, or Basic, istallatio optio for SharePoit 2010, the setup program istalls SQL Server 2008 Express by default as the back-ed database provider. You should patch SQL Server 2008 Express to the same versio as SQL Server 2008 s full editios, SP1 with CU2, CU5, or greater. SQL Server 2008 R2. Microsoft supports SharePoit 2010 o the 64-bit versio of SQL Server 2008 R2. Ay available editio of SQL Server 2008 R2 (Developer, Workgroup, Stadard, ad Eterprise) is supported with SharePoit, subject to the editio s limitatios, as log as it is 64 bit. SQL Server 2008 s R2 release adds eve more fuctioality to the platform, icludig busiess itelligece tools such as PowerPivot, improved admiistrative features, ad tighter itegratio with SharePoit. SQL Server 2008 R2 Express. SQL Server 2005 Express is a free editio of SQL Server 2005 distributed by Microsoft for use i small applicatios or eviromets. The major chage to the Express editio for SQL Server 2008 R2 is that databases are ow limited to 10GB of storage istead of just 4GB.

169 152 SharePoit 2010 Disaster Recovery Guide Note: Oe adjustmet to the list of database platforms for SharePoit 2010 that you should take ote of is the retiremet of the use of SQL Server 2005 Embedded Editio (also kow as the Widows Iteral Database or WID). I Widows SharePoit Services (WSS) v3, the WID was automatically used as the back-ed database host for all-i-oe istallatios, but SharePoit Foudatio 2010 ow uses SQL Server 2008 Express as its database host for all-i-oe istalls, just like SharePoit Server 2010 does. This does make it easier to keep all of the istallatio optios for SharePoit 2010 straight, but it is worth keepig i mid because it does mea you are facig a hard cap o the size of your Share- Poit databases due to the limitatios of the Express licese. Sice the release of SQL Server 2008, Microsoft has made a large amout of iformatio ad data available regardig its beefits over the previous SQL Server 2005 release, both i geeral terms ad specifically regardig SharePoit. Use of SQL Server 2008 ca offer a improved admiistrative experiece, backup compressio fuctioality, richer aalysis of busiess itelligece data, ad much more. I additio to these beefits, SQL Server 2008 is expected to offer a much loger period of support coverage from Microsoft tha SQL Server 2005 give its more recet etrace ito the marketplace. Fially, it is worth metioig that SQL Server 2008 was the database platform used by Microsoft durig the developmet of SharePoit 2010, allowig the SharePoit product team to take full advatage of SQL Server 2008 s feature set rather tha targetig the less advaced SQL Server The material covered i this chapter primarily discusses the use of SQL Server 2008 i a Share- Poit eviromet. Much of the cotet also applies to SQL Server 2005, but there are cases whe it does t. If you are lookig for cotet specifically pertaiig to SQL Server 2005, you should look ito purchasig SharePoit 2007 Disaster Recovery Guide, which offers two chapters specifically devoted to backup/restore ad high availability for that database platform. The visual examples provided i this chapter were geerated i a testig eviromet usig the followig platforms ad compoets. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 Developer Editio with SP1 (build ) Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 SharePoit. SharePoit Foudatio 2010 Release Cadidate 1 (build 4730) How to Back Up a SQL Server 2008 Database The followig steps walk you through the process ecessary to back up a database i SQL Server 2008 through the SQL Server Maagemet Studio GUI tool. These steps are desiged to give you a idea of what you eed to cosider whe backig up your ow databases ad how you

170 Chapter 7 SQL Server 2008 Backup ad Restore 153 Figure 7.1 Eter the coectio iformatio for the target SQL Server database istace to coect to it via SQL Server Maagemet Studio. could go about the process. As covered later i this sectio, this is ot the oly way to back up your SharePoit databases through SQL Server, ad it may ot be the best optio for you to choose, but it is a startig poit from which you ca better uderstad how SQL Server hadles database backups. Note: The user executig the backup must, at a miimum, have bee grated the db_backupoperator security role withi the target database server to back up a database. 1. Ope SQL Server Maagemet Studio ad coect to the SQL Server database istace hostig the database you wat to back up. Figure 7.1 depicts the coectio dialog box show whe opeig SQL Server Maagemet Studio. Note: SQL Server Maagemet Studio is the graphical user iterface (GUI) cliet maagemet tool provided with SQL Server 2008 to admiistrate database istaces ad databases ruig o the platform. It is istalled by default o all servers hostig SQL Server 2008 ad ca be idividually istalled o cliet computers to allow for coectios to remote SQL Server hosts.

171 154 SharePoit 2010 Disaster Recovery Guide Figure 7.2 SQL Server Maagemet Studio with a database selected for backup. 2. Oce SQL Server Maagemet Studio coects to the target database istace ad opes, the cotets of the istace are displayed i the tree view of the Object Explorer pae (which, by default, opes o the left side of the widow). Expad the Databases etry i the Object Explorer, ad fid the ame of the database targeted for backup. See Figure 7.2 for a example. 3. Right-click o the ame of the database, select the Tasks optio whe the meu opes, ad the click o the Back Up optio (as show i Figure 7.3) to ope the Back Up Database dialog box. 4. The Back Up Database dialog box opes, allowig you to customize the backup operatio to meet your eeds. O the Geeral page (see Figure 7.4), you ca cofigure the source database for the backup ad determie the backup type, the compoets to be backed up, the backup set associated with the backup, ad the destiatio for the file(s) created by the backup operatio. The Optios page (see Figure 7.5) allows you to cofigure settigs for overwritig existig backup files, backup reliability testig, ad hadlig of trasactio logs ad tape drives by the backup operatio. After you have cofigured the backup settigs accordig to your requiremets, click the OK butto to start the backup operatio. Note: The Script drop-dow meu (see Figure 7.6) at the top of the Back Up Database dialog box allows you to create a Trasact-SQL (T-SQL) script that ca be executed to back up your database without the GUI iterface described i these steps. The script created by this process uses the same cofiguratio settigs that you selected i the dialog box. This allows you to cofigure your database backup usig a user-friedly tool ad covert those settigs ito a format that a experieced database admiistrator ca use to automate the backup process. 5. As the backup rus, the Progress box i the lower-left corer of the dialog box (see Figure 7.7) displays a percetage idicatig how much of the backup operatio has bee

172 Chapter 7 SQL Server 2008 Backup ad Restore 155 Figure 7.3 The Tasks Back Up meu optio i SQL Server Maagemet Studio. completed. There is also a lik displayed below the Progress idicator allowig you to cacel the operatio. 6. After the backup is fiished, a message box statig The backup of database <your database s ame4 completed successfully is displayed (see Figure 7.8). Click the OK butto to retur to the SQL Server Maagemet Studio mai widow. Before movig o to how to restore the target database from the backup file you just created, take a momet to review the cofiguratio optios available for your SQL Server backups. As oted i step 4, you have quite a few optios available for cofigurig your database backup to meet your specific eeds. If possible, it s a good idea to discuss these optios with your database admiistrator before implemetig them to cofirm the correct course of actio to take for your system. Database Recovery Models SQL Server offers three types of recovery models for each database it hosts: Full, Simple, ad Bulk-Logged. The mai differetiatig factor betwee the three recovery models is how the

173 156 SharePoit 2010 Disaster Recovery Guide Figure 7.4 The Geeral page of the Back Up Database dialog box. trasactio logs for a database are maaged ad backed up. By default, a database uses the same recovery model as the SQL Server system-level model database, which should be Full if the settig is ot chaged after istallatio. Of course, SharePoit is a bit of a exceptio to that rule. Because SharePoit s istallers ad tools create its databases, those databases follow a differet set of rules tha databases created directly i SQL Server. Each sectio that follows otes which SharePoit databases are created with the related recovery model. If you wat to chage the recovery model of a SharePoit database oce it is created, you ca modify it i the SQL Server Maagemet Studio via the database s properties or via a T-SQL commad. Full Recovery Model As its ame implies, the Full recovery model protects data about every trasactio made i the database by requirig that a backup of the database s trasactio log be made alog with oe of the database. By icludig a backup of every trasactio for the database, the Full recovery model is the oly model that allows for a database to be restored to a specific time i its history. You should use the Full recovery model if your data is missio critical ad you eed the ability to restore backups to a specific poit i time. For the Full recovery model to be completely

174 Chapter 7 SQL Server 2008 Backup ad Restore 157 Figure 7.5 The Optios page of the Back Up Database dialog box. Figure 7.6 The Script drop-dow meu of the Back Up Database dialog box. effective, you must make regular backups of both your database s data ad log files. By default, SharePoit s Cofiguratio database, the databases associated with the Cetral Admiistratio site, ad ay cotet databases created through Cetral Admiistratio, PowerShell, STSADM, or the SharePoit object model are set with the Full recovery model.

175 158 SharePoit 2010 Disaster Recovery Guide Figure 7.7 The Progress idicator shows the status of the backup operatio as it rus. Cautio: Whe evaluatig recovery models, keep i mid the storage implicatios of choosig oe model over aother, i additio to what backup ad restore data is beig retaied. Because the Full recovery model allows you to record every trasactio executed i a database by also backig up the trasactio log, it requires a great deal more space to store that data withi the database s trasactio logs. You may fid that you are preveted from usig the Full recovery mode due to a lack of available storage, i which case you must keep i mid the impact that has o how you ca restore your databases. Simple Recovery Model The Simple recovery model retais the least amout of iformatio about the database beig backed up. No trasactio logs are backed up, meaig that the database ca oly be restored to the most recet full or differetial database backup, ot to a specific poit i the database s trasactioal history. The Simple recovery model is ideal whe your data is ot critical (such as a developmet eviromet), is ot subject to frequet chage (ot a likelihood for a Share- Poit database), or is ot a requiremet to recover all trasactios sice the last backup. By

176 Chapter 7 SQL Server 2008 Backup ad Restore 159 Figure 7.8 Whe the backup operatio is completed, SQL Server Maagemet Studio displays a completio dialog box. default, databases associated with SharePoit Service Applicatios, such as the Search databases, are set with the Simple recovery model. Bulk-Logged Recovery Model The Bulk-Logged recovery model represets a middle-groud optio betwee the Full ad Simple recovery models. Like the Full recovery model, the Bulk-Logged recovery model requires the database s trasactio log to also be backed up, allowig it to track trasactios made i the database. The Bulk-Logged recovery model is desiged to reduce the loggig of bulk operatios such as data imports ad idex maagemet actios to a miimum, providig some of the performace beefits of the Simple recovery model. Microsoft recommeds oly usig the Bulk- Logged recovery model i specific circumstaces, switchig to it prior to bulk operatios ad the returig to the Full or Simple models oce the bulk operatios are completed. Database Backup Types SQL Server 2008 offers several types of backups that ca be made for the databases hosted i a istace: full, differetial, partial, ad trasactio log. Each optio is desiged to provide a

177 160 SharePoit 2010 Disaster Recovery Guide uique set of beefits to meet a variety of eeds ad use cases, but each comes with its ow uique set of drawbacks as well. Whe cosiderig which backup type to use for each of your SharePoit databases, cosider these attributes i cojuctio with the use of the specific database. Some databases may eed to be restored quickly, for example, i which case it may make sese to use full backups o a frequet basis. O the other had, differetial backups typically require less storage space tha full backups, but they ofte take loger to restore. This is just oe example of a trade-off you must cosider. The selectio ad applicatio of backup types i your eviromet ca have serious implicatios o the effectiveess ad cost of your SharePoit implemetatio. Note: SQL Server 2008 stores a database i the file system of a host server across a set of files. You ca group these files ito collectios kow as file groups for ease of allocatio ad admiistratio. Each database must have at least oe data file ad oe log file, although it ca possess more tha oe. If you use multiple files for a SharePoit cotet database, Microsoft strogly recommeds that you protect it with SQL Server s backup ad restore tools istead of SharePoit. SharePoit s restore tools caot restore a database with multiple files as effectively as SQL Server s tools ca. The list that follows defies each backup type withi the cotext of SQL Server ad discusses its commo use cases. Full. A full database backup backs up the etire database, icludig its full data files ad the trasactio log compoets ecessary to allow the whole database to be recovered. Because a full backup ecompasses everythig associated with a database, its output requires the most storage space. Additioally, a full backup of a database is required before ay other type of backup ca be made for that database. Differetial. A differetial backup of a SQL Server database oly icludes the data i the database that has chaged sice the last full backup was made of the database. Differetial backups ca be requested for a database or oe of its files or file groups. The biggest advatage of a differetial backup is that it does t take up as much space as a full backup ad ca be completed more quickly. As oted i the previous bullet, you must first perform a full backup of a database before the differetial optio becomes available. Note: To restore a differetial backup, you must first restore its associated full backup set or iclude that full backup set i the requested restore operatio. Partial. Partial backups are desiged to provide a smaller ad faster backup alterative for large databases with multiple file groups. Partial backups always iclude the database s primary file group ad ay other file groups set as writeable. If a database is set to be

178 Chapter 7 SQL Server 2008 Backup ad Restore 161 read-oly, a partial backup of that database icludes oly the primary file group. The partial backup optio was origially desiged for read-oly databases usig the Simple recovery model, but you ca also use it with read-write databases ad the Full ad Bulk-Logged recovery models. File. You ca back up a database s data file (or files) idividually. If a sigle file is corrupted or deleted, backig up the idividual files ca allow for a speedier recovery because oly the affected file has to be restored. This ca become complex if your database has a large umber of files associated with it or overdo it if you have oly oe file for your database, so you should oly use it i whe your database eviromet has specific eeds or requiremets for file backups. Copy-oly. Most types of SQL Server backups have a actual impact o the source database, affectig how the backup (as well as subsequet backups) are restored. Oe method that is a exceptio to this is the copy-oly backup, which is specifically iteded to ot modify the target database i ay way whe the backup is made hece the use of the term copy. Usually, makig a backup chages the database ad affects how later backups are restored. Normal backup types chage a database s log archive poit, which creates a eed to properly sequece backups so that you ca properly apply trasactio logs whe restorig these backups. Copy-oly backups remove the eed for that sequecig, so if it or the orderig of the backup files for it is iterrupted, you ca still restore the database. Trasactio log. A trasactio log backup creates a backup copy of the log files detailig all the modificatios that have bee made to a database over time. Trasactio log backups are available oly with the Full ad Bulk-Logged recovery models; because the Simple recovery model does ot offer the ability to recover to a specific poit i time, there is o eed to track chages that have bee made to a database. Trasactio logs are also importat to preserve because of the role they ca play i other SQL Server high availability (HA) fuctioality, such as database mirrorig ad log shippig. Additioally, trasactio log backups play a vital role if you are usig the Full recovery model for your database; to do a full recovery with that model, you must have completed a full backup ad at least oe trasactio log backup of your database. Performig frequet trasactio log backups also keeps the database s trasactio logs from takig up too much space o the database because they are trucated as part of the backup process, allowig SQL Server to delete them ad reclaim disk space. Note: SQL Server writes all its actios to a database s trasactio logs immediately after the actios are requested, before chages to the database are actually completed. This esures that the requested chages to the database are recorded ad preserved i the trasactio logs should a system failure or data corruptio occur durig executio.

179 162 SharePoit 2010 Disaster Recovery Guide Backup Expiratio Settigs I the Backup Set sectio of the Geeral page i the Back Up Database dialog box, you ca cofigure specific expiratio settigs for your database backup. Depedig o the radio butto you select, your backup ca expire after a specified umber of days or o a specific date. The optio butto for the After optio is selected by default i the Back Up Database dialog box, ad the Days field value is set to 0. You ca modify this default value by cofigurig the media retetio settig withi SQL Server s cofiguratio optios. If you are backig up your database via a maiteace pla or regularly scheduled backup, specifyig a value for this settig prevets SQL Server from overwritig your backup file util the umber of days or date threshold has bee met. Cautio: Settig a expiratio value for your backup does ot prevet it from beig overwritte by applicatios or users outside of SQL Server. You ca still delete the files through the file system or overwrite them i their storage locatio. Backup Destiatios Ulike SharePoit, SQL Server ca back up its databases directly to a tape storage locatio attached to the server i additio to a server s hard disk. I the Destiatio sectio of the Geeral page i the Back Up Database dialog box, you ca eter up to 64 paths by clickig the Add butto ad avigatig to the desired storage locatio. This allows you to simultaeously create multiple copies of your backup files without maual itervetio. You ca also remove a backup path from the list by selectig it ad clickig the Remove butto. Selectig a path ad clickig the Cotets butto displays summary iformatio for the backup ad a list of the backup sets associated with it. Note: The locatio you select for your backup media set must be associated with or available from the server hostig the SQL Server istace that you are coected to. So if you are ruig SQL Server Maagemet Studio o your workstatio ad coectig to a remote database istace, you are oly able to save the backup to a file system directory or attached tape drive o the database host server, ot o your local workstatio. Oce the backup is created, you ca copy it to your local workstatio if you desire, but you caot create backup files o your local workstatio through the backup operatio. Overwrite Existig Backup Media The Overwrite Media sectio of the Optios page i the Back Up Database dialog box allows you to determie how SQL Server hadles ay existig files i the backup storage locatio that were created by a previous backup operatio. (See Figure 7.5 for a example of the Optios

180 Chapter 7 SQL Server 2008 Backup ad Restore 163 page.) You have the optio to add your curret backup s data to the existig backup media set or create a ew backup media set ad have SQL Server erase the previous files. If you chose to use the curret media set, you still ca decide whether to apped your data to the existig files i the media set or overwrite it. You are also give the optio to have SQL Server look for potetial amig ad expiratio date coflicts betwee the media sets by selectig the Check Media Set Name ad Backup Set Expiratio check box ad eterig a media set ame i the text field. If you chose to create a ew media set, you must eter a ew ame for the media set i the associated text field. Reliability Checks SQL Server 2008 also offers the ability to check a backup media set whe the operatio is fiished to cofirm that the output of the operatio is viable. I the Reliability sectio of the Optios page i the Back Up Database dialog box, you have the optio to require SQL Server to verify the backup files whe the operatio is completed as well as to request a checksum verificatio of the backup before it is writte to its storage media. The backup file verificatio cofirms that the media set has bee writte to its storage media without error. The checksum verificatio cofirms that the data withi the backup media set is cosistet with ay checksums associated with the database to esure that valid data is beig writte to the storage media ad has ot become corrupted. Cautio: As with almost every decisio a iformatio techology (IT) professioal must make throughout the course of a day, there are potetial drawbacks to performig reliability checks that must be take ito accout. Specifically, these checks ca have a sigificat egative impact o the database s throughput while they are beig performed ad utilize a great deal of the host server s available CPU processig power, both of which ca cause a serious degradatio of the database s performace. It is importat to determie how ecessary it is to perform reliability checks o your database s backup ad whe these activities are occurrig if requested so that coflicts with periods of high user activity ca be avoided. Database Sapshots Origially itroduced with SQL Server 2005, database sapshots offer admiistrators aother optio for creatig a poit-i-time view of a database o top of SQL Server s ormal backup fuctioality. Database sapshots capture a fixed viewpoit of a target database, icludig all of its state ad cotet except for ay ucommitted trasactios. Database sapshots are attractive because they ca take up much less storage tha a backup file by oly trackig the chages made to a database after a sapshot is made, but this is ot always the case, especially for databases that are frequetly updated (such as heavily trafficked SharePoit collaboratio cotet databases). Accordig to Microsoft, sapshots are best used as a reportig resource (creatig a view

181 164 SharePoit 2010 Disaster Recovery Guide of the database at a specific poit i time for later aalysis) or for immediate protectio of a database prior to a major update, but ot as a regular or scheduled backup solutio. Note: SQL Server s database sapshot capability is available oly i Developer ad Eterprise Editio SKUs for SQL Server 2005, 2008, ad 2008 R2. Ulike previous versios of the platform, SharePoit 2010 icludes ative support for SQL Server database sapshots. You ca explicitly create, delete, ad maage sapshots through PowerShell ad custom code that is writte agaist the SharePoit object model. I additio, a umber of platform fuctios iclude support for leveragig database sapshots i their operatios. For example, the Backup-SPSite PowerShell cmdlet icludes a UseSqlSapshot switch that allows you to perform a site collectio backup agaist a sapshot of a cotet database rather tha the actual database. Usig a sapshot for this operatio removes the eed to lock the site collectio to prevet update ad write operatios to the database whe the backup is beig performed. Whe the backup operatio is complete, the cmdlet takes care of cleaig up the database sapshot that was used. The et effect is that users ca cotiue to operate as they ormally would without iterferece from the backup operatio. Sapshots are ot a replacemet for backup ad restore operatios, but you ca leverage them to ehace or improve the overall admiistrative experiece associated with these types of tasks. Mirrored Backup Media Sets Aother feature oly available i the Eterprise SKU for SQL Server 2005, 2008, ad 2008 R2 but relevat to the topic of disaster recovery is mirrored backup media sets. Mirrored backup media sets allow a database to be backed up to multiple backup storage locatios with a sigle operatio, addig greater redudacy to backup operatios ad protectio from storage hardware failure. Mirrored backups ca use either disk or tape as the target storage medium, but the same type of hardware must be used for all mirrored targets i a give operatio. A sigle operatio ca iclude up to four mirrors of the database, ad restoratio of mirrored backup sets allows for every mirror withi the set to be used as the source for the restore. Mirrored backup media sets provide a additioal optio for icreasig the redudacy of your SQL Server DR solutio, but they ca easily come with a additioal cost, thaks to the requiremet for additioal storage media, ot to metio the SQL Server Eterprise Editio licese. What s New i SQL Server 2008 Backup Microsoft added several ew features ad ehacemets to the SQL Server platform with its 2008 release. These iclude spatial data types for itegratig geographical data ito applicatios, the ability to maage multiple SQL Server 2008 hosts from a sigle locatio usig policybased maagemet, ad data compressio to reduce the amout of storage database files eed ad improve disk iput/output (I/O) ad memory utilizatio. This chapter is about SQL

182 Chapter 7 SQL Server 2008 Backup ad Restore 165 Server 2008 backup ad restore, though, so let s focus o what s ew i that area: backup compressio. Backup compressio is a feature completely ew to SQL Server It was ot possible i SQL Server 2005 to compress database backups i ay way with the out-of-the-box tools available for SQL Server. I SQL Server 2008, backups ca be automatically compressed whe they are created without impactig the targeted database. Compressio is available for all types of database backups, icludig log backups. Additioally, whe a compressed backup is restored ito SQL Server 2008, the data stored i it is automatically ucompressed. This meas that the restore process for compressed backups is o differet from the restore process for ucompressed backups. It may seem that the biggest advatage of this backup compressio feature is its ability to use less storage space to retai a backup, allowig you to reduce your storage usage ad costs. Although this is defiitely a beefit, there is aother gai that ca be equally valuable to your eviromet, if ot greater: reduced disk I/O. Whe you compress the backup file, it takes less time to write the backup file to your disk ad frees up that I/O for more critical activities, such as writig uploaded documets ito a SharePoit cotet database or updatig a Search crawl database. Depedig o the resources available for your database servers, this ca positively affect your performace over ucompressed backups. This is true especially if, oce these smaller files are created, you ca trasfer them more quickly tha ucompressed backups via a etwork coectio that may have restrictios o its badwidth, such as a local area etwork (LAN), WiFi, or a wide area etwork (WAN), to a remote storage repository. Keep i mid, though, that this ew feature i SQL Server 2008 has some drawbacks. First ad foremost, a performace trade-off happes durig compressio: although your disk I/O impact is reduced, the CPU utilizatio that is ecessary icreases to allow the server to perform the compressio fuctio. The good ews is that, overall, the usual result from backup compressio is better overall performace, but you eed to keep a eye o CPU ad disk performace metrics i your eviromet to uderstad exactly what the beefits of usig backup compressio are for your SharePoit databases ad if they are worth the cost. Tip: You ca also mitigate some of the risk that backup compressio presets to your CPU performace by takig advatage of aother ew feature i SQL Server 2008: the Resource Goveror. With the Resource Goveror, you ca limit the utilizatio of your server s CPU resources by the backup process so that it does ot affect other more importat processes durig peak loads. To eable compressio of a backup for a database, locate the Compressio sectio o the Optios page of the Backup Database dialog box, ad select the desired optio from the Set Backup Compressio pull-dow meu. For a example of the Compressio sectio, see the

183 166 SharePoit 2010 Disaster Recovery Guide bottom of Figure 7.5. By default, compressio is ot eabled for databases i SQL Server You must select to compress the database i the dialog box s Optios page, cofigure it as a settig i a T-SQL backup script, or chage the default settig for the etire SQL Server istace if you wat to use the fuctio. Fially, you should ote some limitatios to the use of backup compressio prior to implemetig it i your eviromet. Make sure you closely review the list that follows ad uderstad how its poits ca apply to your SharePoit eviromet ad its use of SQL Server 2008 before you take advatage of backup compressio. SQL Server 2008 licese. Backup compressio is available oly with the Eterprise SKU for SQL Server The good ews is that if you are ruig SQL Server 2008 R2, backup compressio is available with both the Stadard ad Eterprise SKUs. Backups lack compatibility with previous versios of SQL Server. You caot restore compressed backups created with SQL Server 2008 ito older versios of SQL Server such as SQL Server 2005 or Lacks compatibility with Trasparet Data Ecryptio (TDE). If your database has TDE eabled, you caot compress its backups. There is aother ew feature i SQL Server 2008 that may ot seem to be directly related to the topic of backup ad restore, but it does provide some iterestig implicatios ad circumstaces to cosider i your disaster recovery plaig for your SQL Server 2008 databases: Remote Biary Large Object (BLOB) Storage, or RBS for short. The direct implicatios of RBS are discussed i the What Caot (or Should Not) Be Backed Up sectio that follows, but it is importat to first set the stage with a descriptio of this feature. A BLOB is commoly backed by a variable-legth SQL Server colum data type that allows for large amouts of biary data, such as a Microsoft Word documet or a ecrypted file, to be stored directly i a SQL Server database table rather tha i a file system directory. Traditioally, SharePoit has made heavy use of BLOB colums i its database tables, storig documets uploaded ito a site directly i these colums. SharePoit 2010 is o differet i that regard. BLOBs offer much flexibility so that SharePoit ca hadle a rage of file types ad sizes, but they ca also cosume a great deal of storage space ad computatioal resources o a SQL Server istace. To try to alleviate the pressure that BLOB usage ca place o SQL Server, Microsoft itroduced the RBS feature with SQL Server 2008, which allows BLOB data to be stored i a remote locatio but still be accessed via SQL Server. RBS eables SQL Server to desigate exteral cotet addressable stores (CAS) as dedicated storage repositories for BLOB data that still preset to cliet applicatios, such as SharePoit, as if it were stored i a database table directly. RBS uses a flexible provider model so that differet storage solutios ca be chose to meet the specific

184 Chapter 7 SQL Server 2008 Backup ad Restore 167 requiremets of your eviromet. SQL Server provides its ow RBS provider, the SQL FILE- STREAM provider, for use with SQL Server 2008, but third-party providers such as Metalogix s StoragePoit, EMC, ad AvePoit s DocAve Exteder are also available. RBS ca be used with ay editio of SQL Server 2008, but a storage solutio other tha storage locally attached to the host server ca be used oly with the Eterprise editio. The FILESTREAM provider is icluded with SQL Server 2008 at o additioal cost, but it does have some limitig factors to cosider: it ca oly work with a SQL Server host s local drives, it does t support database sapshots or mirrorig, ad it does t support TDE, just to ame a few. I the case of SharePoit 2010, awareess of SQL Server s RBS capability was added as a ew feature. This allows SharePoit to be cofigured cosistetly regardless of how SQL Server s storage is cofigured; at the same time, it allows SharePoit admiistrators ad DBAs to have some flexibility i how SharePoit uses its storage. Although it may seem like this is a feature that would appeal oly to the largest of eterprises, it also provides smaller orgaizatios with appealig flexibility. Oe major chage to the database situatio for SharePoit 2010 is that it is o loger possible to create databases of ulimited size usig the free Widows Iteral Database icluded i a basic istall of Widows SharePoit Services (WSS). The oly free database optio for SharePoit 2010 is SQL Server Express, but its databases are limited to 4GB (SQL Server 2005 ad 2008 Express) or 10GB (SQL Server 2008 R2 Express). You ca overcome that size limitatio with the use of RBS because cotet stored with RBS does ot cout agaist the total size of the database. Tip: The use of RBS as a way to overcome the sizig limitatios of SQL Server Express is likely to be most applicable whe upgradig a WSS v3 eviromet usig the Widows Iteral Database to SharePoit Foudatio or Server If the size of oe or more of the databases i your Widows Iteral Database istace is larger tha your ew target SQL Server Express istace, you are ot goig to be able to migrate it uless you purchase a full SQL Server licese or implemet RBS. If you are thikig about usig SQL Server Express ad RBS because of database sizig issues, i geeral it is a good idea to seriously cosider usig a full SQL Server licese for your SharePoit eviromet istead. SQL Server Express is a good platform, but it does ot provide the same overall scalability, coverage, ad fuctioality of a purchased versio of SQL Server. Also, there are some performace limitatios o SQL Server Express. (It is limited to oly oe core o a server, ad there is t good data available at this time o how RBS performs with SQL Server Express.) If you re cosiderig it as a temporary or short-term part of your migratio strategy, that s great. But it probably is t the way to go if you are t icludig a pla to move to a paid versio of SQL Server i your migratio.

185 168 SharePoit 2010 Disaster Recovery Guide SharePoit ad Backig Up SQL Server 2008 The steps at the begiig of the previous sectio show you oe method by which you ca create a backup of a database i SQL Server 2008; you ca use them to back up pretty much ay database hosted i a SQL Server 2008 database istace. There are other more complex ways to create database backups i SQL Server 2008, such as T-SQL scriptig ad maiteace plas, but as metioed earlier, it is best to leave those more ivolved approaches to the experts. Because you ow have a startig poit for backig up your SharePoit eviromet via SQL Server, it is importat to start thikig about the issues ad restrictios specific to SharePoit that you eed to address whe movig forward with the process. Tip: For the best results whe backig up your SharePoit databases, pla o executig the backup operatios durig periods of reduced user activity i your SharePoit eviromet, such as after ormal busiess hours or durig plaed maiteace periods. Also, avoid schedulig them agaist other scheduled activities withi the farm itself, such as search crawls or usage log processig. This esures that a miimal umber of chages are beig made to your databases while the backups are beig created; i additio, it prevets your ed users from experiecig performace issues whe attemptig to access SharePoit. SQL Server backup operatios ca be resource itesive for their host istaces, ad you should try to avoid impactig SQL Server s ability to serve its data to Share- Poit as much as possible. If you eed to back up a SharePoit database with SQL Server durig ormal busiess hours or whe there is regular or elevated user activity i the sites withi that database, cosider applyig a read-oly site lock for affected site collectios i the SharePoit Cetral Admiistratio site or with PowerShell prior to executig the backup. This actio ca esure that your users do ot ecouter degraded performace whe accessig the site durig a backup operatio, as well as prevet them from tyig up the database whe the operatio is also tryig to use it. This is ot required for a backup operatio but ca reduce the time a backup takes to complete ad the umber of support calls that may be made regardig poor performace. If you are makig a backup through the Cetral Admiistratio site or via a PowerShell cmdlet, SharePoit automatically sets the targeted site collectio to read-oly, but with SQL Server, you must maually cofigure the site collectio before backig it up. What Ca Be Backed Up Above all else, the most importat aspect of your SharePoit eviromet, the reaso it is so importat to your busiess, is what your ed users put ito it. The cotets of your SharePoit sites, whether they are documets, lists, forms, or some other form of kowledge capital, are most likely to be the first ad foremost item that your orgaizatio eeds replaced should

186 Chapter 7 SQL Server 2008 Backup ad Restore 169 disaster strike your SharePoit eviromet. Happily, you ca easily back up SharePoit s cotet databases ad restore them at a later date usig SQL Server s tools, usig either the steps described earlier or the other optios that SQL Server offers. Note: The locatio you select for your backup media set must be associated with or available from the server hostig the SQL Server istace that you are coected to. So if you are ruig SQL Server Maagemet Studio o your workstatio ad coectig to a remote database istace, you are oly able to save the backup to a file system directory or attached tape drive o the database host server, ot o your local workstatio. Oce you create the backup, you ca copy it to your local workstatio if you desire, but you caot create backup files o your local workstatio through the backup operatio. I additio to your SharePoit cotet databases, do t overlook other databases i your SQL Server eviromet that may cotai critical iformatio for your SharePoit eviromet, eve if they are ot explicitly SharePoit databases: SQL Server s system databases. Every SQL Server istace is created with several default databases that are required to store critical data about the state of the istace, such as its MASTER, MSDB, MODEL, ad TEMPDB databases. You ca also back up these system databases if you wat to preserve the most recet state of your SQL Server istace. It may ot be ecessary to do so, depedig o your requiremets for data preservatio ad your ability to rebuild the istace, so you should validate your plas with your SQL DBA, if possible. Of those databases, the MASTER, MSDB, ad MODEL databases are potetial cadidates that you should cosider backig up; the TEMPDB is re-created every time a SQL Server istace is restarted. What Caot (or Should Not) Be Backed Up Much like the out-of-the-box backup tools provided with SharePoit, SQL Server caot back up your SharePoit eviromet s IIS Web server settigs, custom code or site templates, the SharePoit Root directory (also kow as the 14 Hive), or ay other items located i the file system of your SharePoit servers. Because these items are ot stored i a SharePoit database i SQL Server, it stads to reaso that they caot be backed up. Noetheless, it is importat to keep this fact i mid whe developig your comprehesive disaster recovery pla so that you are aware of what holes you eed to fill with alterative tools or approaches. If your SharePoit cotet is beig stored i a RBS-eabled cotet database, you are ot directly backig up BLOB data whe you back up your database; you are simply backig up poiters that are uderstood by the RBS provider that is associated with the database. To protect the BLOB data that is tied to the cotet database, your backup strategy must icorporate your RBS provider; more specifically, you must esure that the storage locatio or locatios that the RBS provider uses are protected by some data protectio strategy. This makes the total protectio

187 170 SharePoit 2010 Disaster Recovery Guide of SharePoit data stored i RBS-eabled cotet databases more difficult, ad ay pla depeds o the ature of the RBS provider. It is importat to uderstad the details of this costrait. It oly pertais to backups performed usig SQL Server s tools, ay other backup tools that operate directly agaist the databases, or ay o-microsoft RBS solutios. If you are backig up a RBS-eabled cotet database with SharePoit backup tools i the Cetral Admiistratio site or PowerShell via the FILESTREAM provider, the database ad its associated BLOBs are backed up together i a sigle operatio because SharePoit s applicatio programmig iterfaces (APIs) hide RBS implemetatio details from the applicatios that use them. If you are usig a third-party RBS provider, Share- Poit 2010 s backup tools do ot iclude those BLOBs; you must maually back them up. The two major aspects of a SharePoit eviromet that we have t covered yet are its cofiguratio (specifically its cofiguratio database) ad its Service Applicatios. Although you ca back up your SharePoit 2010 farm s cofiguratio database ad the databases associated with its Service Applicatios usig SQL Server s tools, you also eed to uderstad how to use the backups of those items. With Service Applicatios, you ca restore a backup of their associated database, but you must have take a backup of the Service Applicatio through the Cetral Admiistratio site or PowerShell ad restored that ito a farm before you ca restore its database. I most cases, SharePoit s built-i tools or a third party backup tool is goig to be a better optio for protectig those items i case of a disaster. There ca be utility i creatig SQL Server backups of the Service Applicatio databases, but it is more as a poit of referece or referral tha for disaster recovery protectio. With the SharePoit farm s cofiguratio database, you ca t restore directly back ito a live farm; there s just o supported way to do it with SQL Server s tools. The good ews with Share- Poit 2010 is that this is ot the ed of the discussio. SharePoit 2010 itroduces several ew tools i the area of backup ad restore. Iterestigly, oe of those tools chages what you ca ow do with SQL Server backups of a farm s cofiguratio database. Oe of SharePoit 2010 s ew PowerShell cmdlets, Backup-SPCofiguratioDatabase, allows you to geerate a cofiguratio database backup of a cofiguratio database attached to your curret farm, a separate farm (assumig the accout ruig the script has the proper rights i that farm), ad most importatly, a cofiguratio database that is ot attached to a farm. This meas you could take a SQL Server backup of your cofiguratio database ad restore that database to a SQL istace i the evet of a disaster. You could the extract the details of the database s cofiguratio usig Backup-SPCofiguratioDatabase. You ca the use this backup like you would ay other cofiguratio database backup created via the PowerShell cmdlet, except that you preserved the data i it via SQL Server s tools istead of SharePoit s. For more iformatio o the ew backup ad restore tools i the Cetral Admiistratio site ad PowerShell, see Chapter 9, SharePoit 2010 Cetral Admiistratio Backup ad Restore ad Chapter 10, SharePoit 2010 Commad Lie Backup ad Restore: PowerShell.

188 Chapter 7 SQL Server 2008 Backup ad Restore 171 Note: This aspect of SharePoit 2010 s ew cofiguratio backup fuctioality is oly possible via the PowerShell cmdlet; the Cetral Admiistratio site ca oly take cofiguratio database backups of the farm it govers. Database Sizig As with ay SQL Server backup operatio, the size of the SharePoit database you are backig up directly iflueces the amout of time that the operatio takes to complete: the larger the database, the loger it takes to fiish. As your databases grow larger, you eed to cotiually evaluate the timig ad approach you take whe backig them up so you ca miimize the impact of your backup operatios o your SharePoit eviromet s ability to serve its users. You may fid that after a certai poit you are o loger able to complete full backup operatios quickly eough to meet your desired schedule. Whe this happes, cosider usig differetial backups or movig some site collectios to ew cotet databases to shorte your backup periods. Moitorig ad maagig the size ad usage of your SharePoit databases should already be a part of your operatioal SharePoit maiteace pla, but these activities become eve more importat whe you start cosiderig disaster recovery. Tip: There is o hard, fast limit o how large a SharePoit site collectio should be. I some cases, SharePoit site collectios ad their associated SQL Server cotet databases have grow to be hudreds of terabytes (TB) large ad still bee viable for ed users. But just because this is possible does ot make it feasible, especially from a disaster recovery perspective. Microsoft recommeds limitig your cotet databases to 200GB ad a idividual site collectio i a database to 100GB uless it is the oly site collectio i a database, but these are ot absolute. Discuss this topic with your orgaizatio s SQL Server DBA, because this perso ofte has prefereces for geeral database size limits that eed to be observed. The good ews is that SharePoit ca be quite flexible whe it comes to its cotet databases, allowig you to associate oe to may of them with a sigle Web applicatio. The mai limitatio is that you caot divide a site collectio across cotet databases, which meas that if a sigle site collectio grows beyod your size restrictios, you must split it ito two collectios or have cotet removed to comply. SharePoit admiistrators also have several commads available, such as the Move-SPSite PowerShell cmdlet, to help them move site collectios from oe cotet database to aother. Aother less obvious item to cosider is how the site collectios withi your SharePoit databases are utilized. If umerous users access the site, collaborate o documets, or update cotet at the same time, it ca directly impact your backup ad restore plaig. These activities lead

189 172 SharePoit 2010 Disaster Recovery Guide to SharePoit readig ad writig to its databases with icreased frequecy, which i tur meas SQL Server is writig a large amout of data to the trasactio logs associated with these databases. Because a full backup of a SQL Server database icludes the database s active trasactio logs, heavy usage of your sites adds to the time it takes to back up (ad restore) the databases associated with them. If you fid that this is egatively affectig your ability to preserve your SharePoit farm s databases, you may eed to reevaluate your farm ad site hierarchies to better distribute use traffic across databases. Note: The previous database sizig issues have a similar impact o SQL Server restore operatios. Oe reaso it is importat to test both your backup ad restore strategies is so that you have a accurate estimate of how log each activity should take i expected coditios. If your restore operatios are takig hours to execute due to the size of your databases ad your system eeds to be available as soo as possible, you are better served by fidig that out through testig rather tha the first time you execute your disaster recovery pla durig a outage that is costig you real moey every secod. How to Restore a SQL Server 2008 Database Backup As with the previous walkthrough of how to back up a database i SQL Server 2008, the followig steps give you a geeral idea of what is ivolved i restorig a backup of a existig database through the SQL Server Maagemet Studio. This is ot the oly way you ca restore a database i SQL Server ad is ot ecessarily goig to be the best approach for you to take with your SharePoit eviromet ad its specific eeds. These steps are iteded to get you thikig about the eeds ad requiremets for your eviromet ad the iformatio you eed to have o had before you execute a SharePoit database restore through SQL Server. Cautio: If the database beig restored is ot curretly hosted i the target database istace, the user must have CREATE DATABASE permissios i the istace to restore the database. If the database already exists i the target database istace, the user must be assiged the sysadmi ad dbcreator server roles i the istace or be the ower (also kow as the dbo) of the database. If a password has bee assiged to the backup media set beig used i the restore operatio, that value must be provided for SQL Server to execute the restore. 1. Ope SQL Server Maagemet Studio ad coect to the SQL Server database istace to which you wat to restore the database backup. 2. Whe SQL Server Maagemet Studio coects to the target database istace ad opes, the cotets of the istace are displayed i the tree view of the Object Explorer

190 Chapter 7 SQL Server 2008 Backup ad Restore 173 Figure 7.9 Select the Restore, Database optio from the Tasks meu. pae (which by default opes o the left side of the widow). Expad the Databases etry i the Object Explorer, ad fid the ame of the database targeted to be overwritte with a previously created backup. 3. Right-click o the ame of the database, select the Tasks optio whe the meu opes, select the Restore optio, ad the click o the Database optio to ope the Restore Database dialog box. See Figure 7.9 for a example. Tip: This actio automatically takes the target database offlie ad prevets other applicatios or processes from accessig it. Wheever possible, attempt to udertake a restore operatio durig a period of advertised or regular dowtime for your SharePoit eviromet. 4. The Restore Database dialog box opes, allowig you to customize the restore operatio to meet your eeds. O the Geeral page (see Figure 7.10), you ca cofigure the database to be restored, determie the source of the backup set used i the restore operatio, ad select the specific backup set used to restore the database. The Optios page (see Figure 7.11) allows you to cofigure settigs for overwritig the existig database, preserve replicatio settigs, prompt before each restore activity, restrict

191 174 SharePoit 2010 Disaster Recovery Guide Figure 7.10 The Geeral page of the Restore Database dialog box. access to the database oce it is restored, cofigure where the database s files are restored o the server s file system, ad determie the type of recovery state the database is placed i whe the restore operatio is completed. After you have cofigured the restore accordig to your requiremets, click the OK butto to start the restore operatio. Note: As with the Back Up Database dialog box, the Script drop-dow meu at the top of the Restore Database dialog box allows you to create a T-SQL script that you ca execute to restore your database without the GUI iterface described i these steps. 5. As the restore operatio executes, the Progress box i the lower-left corer of the dialog box displays a percetage idicatig how much of it has bee completed. There is also a lik displayed below the progress idicator allowig you to cacel the operatio. 6. Oce the restore is fiished, a widow statig The restore of database <your database s ame4 completed successfully is displayed (see Figure 7.12). Click the OK butto to retur to the SQL Server Maagemet Studio mai widow.

192 Chapter 7 SQL Server 2008 Backup ad Restore 175 Figure 7.11 The Optios page of the Restore Database dialog box. Similar to database backups through SQL Server Maagemet Studio, several cofiguratio optios are available i the Restore Database dialog box. You ca use these optios to specify the backup set that is used for the restore, where the backup is restored to, the state the database is placed i whe the restore is fiished, ad much more. Agai, discussig these optios with your database admiistrator is highly recommeded so that you ca determie the best cofiguratio to use with your eviromet. Restore Destiatio Optios The first sectio of the Restore Database widow s Geeral tab, titled Destiatio for Restore, ot oly allows you to select where the backup is restored withi the target database istace, but allows you choose a specific poit i time where you wat the database restored. I the To Database field, you ca select a database from the drop-dow meu to be overwritte by the backup, or you ca type the ame of a existig or ew database as the restore target. By default, the database displayed i the field is the database you right-clicked o to ope the Restore Database widow. The drop-dow meu is populated with all the databases hosted by the database istace. The ext field, To a Poit i Time, is grayed out (disabled) by default ad cotais the text Most recet possible, idicatig that the database will be restored to its coditio whe the backup

193 176 SharePoit 2010 Disaster Recovery Guide Figure 7.12 Whe the restore operatio is completed, SQL Server Maagemet Studio displays a completio dialog box. Figure 7.13 The Poit i Time Restore dialog box. set was created. To chage this settig, click the ellipses ( ) butto to the right of the disabled text field. Doig so opes the Poit i Time Restore dialog box (see Figure 7.13). Note: The Poit i Time Restore optio is ot available for databases cofigured to the Simple recovery model. I this widow, the optio The Most Recet State Possible is iitially selected, ad the Date ad Time fields are disabled. To select a specific poit i time for the database to be restored to, select the A Specific Date ad Time optio butto, which eables the Date ad Time fields. Clickig the Date drop-dow meu displays a caledar cotrol (see Figure 7.14), where you ca avigate to the specific date desired. You ca update the Time field by either typig the desired value for each digit of the time or usig the Up ad Dow arrows to the right of the text field to select the correct umerical value.

194 Chapter 7 SQL Server 2008 Backup ad Restore 177 Figure 7.14 The Date drop-dow meu of the Poit i Time Restore dialog box. Note: Selectig a date more recet tha the date the target backup set was created, or a date that lies i the future, results i the database beig restored to the most recet possible state. Restore Source Optios I the Source for Restore sectio of the Restore Database widow s Geeral tab (see Figure 7.10), you ca specify which backup set is used to restore your database. By default, the From Database optio butto is selected, ad the drop-dow meu ext to it is populated with the ame of the database you right-clicked to ope the Restore Database widow. This meu is populated with the databases hosted i the istace that have previously had backup sets created for them; if a database has ot bee backed up, it does ot appear i this list. If the target database has ot bee backed up with SQL Server before, this field is blak. Selectig a differet database i the From Database drop-dow meu results i the Select the Backup Sets to Restore list box beig updated to show the backup sets associated with the selected database. If the Select the Backup Sets to Restore list box displays more tha oe backup set, you ca select the desired backup set by clickig its check box. Selectig the From Device optio butto disables the From Database drop-dow meu ad the Select the Backup Sets to Restore list box. To select a device as the source of the backup, click the ellipses ( ) butto to the right of the disabled From Device text field. This opes the Specify Backup dialog box (see Figure 7.15), where you ca select a file, tape, or device to be used as a backup source for the restore operatio. You select your type of device from the Backup Media drop-dow meu (File, Tape, or Backup Device, depedig o the types of devices that are

195 178 SharePoit 2010 Disaster Recovery Guide Figure 7.15 The Specify Backup dialog box. attached to your system) ad the click the Add butto to add a istace of the selected device type. A dialog box opes, allowig you to select the desired backup from a list. See Figure 7.16 for a example of the Locate Backup File widow. After selectig a backup, click the OK butto to close the widow ad retur to the Specify Backup widow with your selected backup displayed i the Backup Locatio field. You ca remove the backup selectio by clickig the Remove butto, ad you ca view the items i the backup by clickig the Cotets butto. Clickig the OK butto saves your cofiguratio ad returs you to the Restore Backup widow, where your selected backup is ow show i the Select the Backup Sets to Restore list box. Note: Keep i mid that you must store the backup files to be used i the restore operatio i a locatio you ca access from the server hostig the target database istace. If you store the files o a ucoected device, such as your local workstatio, you must copy the files to the server, map a coectio o the host server to your local workstatio, or place the files i a server-accessible etwork locatio. Restore Optios The first sectio o the Optios tab of the Restore Backup widow, Restore Optios, cotais four check boxes that you ca select to cofigure differet aspects of the requested restore operatio. By default, all four check boxes are uchecked. Overwrite the Existig Database. Whe you select this optio, the restore operatio completely overwrites a existig database ad its associated files if its ame matches the database listed i the To Database field o the Geeral tab.

196 Chapter 7 SQL Server 2008 Backup ad Restore 179 Figure 7.16 The Locate Backup File widow. Preserve the Replicatio Settigs. This optio allows you to keep the origial replicatio settigs of the database i the backup set whe restorig it to a server differet from the server the database was backed up o. If the ew server hostig the database has differet replicatio settigs tha the origial host, selectig this optio prevets the server from overwritig the restored database with its local settigs. It ca be used oly whe the Leave the Database Ready to Use by Rollig Back the Ucommitted Trasactios optio is selected i the Recovery State sectio. Note: Microsoft does ot support the use of SQL Server 2008 s replicatio fuctioality with SharePoit. Prompt Before Restorig Each Backup. This optio prompts the user for cofirmatio prior to restorig each backup set requested by the restore operatio, which ca be helpful whe you eed to pause the restore operatio for activities such as swappig backup tapes.

197 180 SharePoit 2010 Disaster Recovery Guide Restrict Access to the Restored Database. Selectig this optio limits access to the database whe the restore operatio has completed to the followig SQL Server security roles: db_ower, dbcreator, orsysadmi. Below the four check boxes is the Restore the Database Files As list box. This list box displays each of the database files associated with the database i the backup set, showig the full path ad ame of the file as it existed whe the backup was created ad the full path ad ame that it has whe the restore operatio is completed. You ca modify the destiatio path ad ame of ay file i the list box by clickig the ellipses ( ) butto to the right of the Restore As colum for the file you wat to chage. This actio opes a widow titled Locate Database Files, which is similar i appearace to Figure 7.16 s Locate Backup File widow. Select the desired destiatio locatio i the widow s tree directory, ad click the OK butto to retur to the Restore Database widow. Recovery State The Recovery State sectio of the Optios tab cotais three radio buttos that determie what coditio the database is i oce the restore operatio is completed. Leave the Database Ready to Use by Rollig Back the Ucommitted Trasactios. This optio is selected by default ad allows for the restored database to be immediately used oce the restore operatio has completed. This optio is also kow as Restore with Recovery. Leave the Database No-Operatioal ad Do Not Roll Back Ucommitted Trasactios. This optio keeps the database i a restorig state after the requested restore operatio has completed, which is useful whe restorig a database with multiple trasactio logs or whe restorig a sequece of backups to a database (such as a full backup followed by a differetial backup). You caot use the database util a subsequet restore operatio usig the first optio i this list has bee completed. This optio is also kow as Restore with No Recovery. Leave the Database i Read-Oly Mode. This optio allows a database to remai i a restorig state but makes read-oly access to the database available whe the requested restore operatio is completed. This optio creates a stadby file o the local file system of the server hostig the database istace to allow for the actios of the restore operatio to be udoe. This optio is also kow as Restore with Stadby. Below the three optio buttos is the Stadby File text field, which is eabled oly if the Leave the Database i Read-Oly Mode optio butto is selected. To chage the locatio of the stadby file, modify the text i the text field or click the ellipses ( ) butto to the right of the Stadby File text field. Doig so opes a widow titled Locate Rollback Udo File, similar i appearace to Figure 7.16 s Locate Backup File widow. Select the desired destiatio

198 Chapter 7 SQL Server 2008 Backup ad Restore 181 locatio for the stadby file i the widow s tree directory, ad click the OK butto to retur to the Restore Database widow. Note: The stadby file is simply a copy of the existig database. If the file group for the target database is 20GB, for istace, the stadby file requires a additioal 20GB of available disk space. If there is ot eough storage space for the stadby file i the file system at the locatio specified, the restore operatio fails. SharePoit ad Restorig a SQL Server 2008 Backup Ufortuately, restorig a SharePoit database is ot as simple as executig the previous steps to restore your eviromet. Because SharePoit is costatly accessig, readig from, ad updatig its databases, you must take certai precautios to avoid icosistet or corrupted data. The followig sectios detail the steps you must take, depedig o the restore situatio, as well as some other cosideratios whe plaig your restore strategy for your SharePoit databases. Overwritig SharePoit with a Restore of a SQL Backup Although ot may additioal steps are required to restore a SharePoit database i SQL Server for a existig ad operatioal SharePoit farm, the followig steps are importat to esure the itegrity ad stability of the data i your system: 1. Oe importat step to take before makig chages to your eviromet is to lock dow ay affected SharePoit site collectios so that users do ot receive icosistet or icorrect data durig the restore, or lock up resources that may eed to be accessed or writte by the process. Although it may seem attractive to set site collectios withi a targeted database to Read-Oly or No Access, this ca be time-cosumig through the Cetral Admiistratio site, especially if the database has several site collectios. It is goig to be far simpler to use a PowerShell script leveragig the Set-SPSite cmdlet ad its LockState iput parameter or to completely remove the cotet database from the farm via the Maage Cotet Database page i the Cetral Admiistratio site. Regardless of how you do it, iitially you should make sure that users caot tie up items with affected site collectios to esure the best experiece for you ad your users durig the process. 2. Microsoft recommeds that if the SharePoit 2010 Timer service o the SharePoit server hostig your farm s Cetral Admiistratio site is ruig, you should stop it via the Services maagemet cosole sap-i o the server before proceedig with the database restore. Do t restart the Timer service util the database has bee fully restored. This is a good practice, but it may affect what your ed users experiece if they are usig your farm while the Timer service is stopped. Cosider commuicatig with

199 182 SharePoit 2010 Disaster Recovery Guide your users regardig a potetial outage, ad uderstad how this actio i geeral might impact ay service-level agreemets (SLAs) that you have i place. 3. Ope SQL Server Maagemet Studio ad the Restore Database widow for the target SharePoit database to be restored i SQL Server. 4. Whe the Restore Database widow opes, cofirm or modify the destiatio ad source data, ad the select the Optios tab to ope it. 5. Uless you have specific requiremets or eeds for your SharePoit eviromet, the Overwrite the Existig Database check box is the oly Restore optio that you should select. 6. I the Recovery State sectio, select the Restore with Recovery radio butto if you are icludig all the database s trasactio logs i the curret restore operatio. If you eed to restore additioal trasactio logs after this operatio, select the Restore with No Recovery optio butto. You should ot use the Restore with Stadby optio whe restorig a SharePoit database. 7. Click the OK butto to iitiate the restore operatio for this database. 8. Oce you ve restored the database, review its settigs to esure that the farm database access service accout is assiged as the Database Ower. You ca check this i SQL Maagemet Studio by right-clickig o the database ad choosig Properties. I the Geeral tab, uder the Database sectio, see the Ower property. If it is ot assiged, use the sp_chagedbower <domai/userame4 Trasact-SQL commad to update the database ower ( Makig the farm database service accout be the database ower assigs this accout the DB Ower security role. 9. If there are additioal databases i your SharePoit eviromet that eed to be restored, repeat steps 1 through 8 as eeded. 10. Oce all databases have bee restored properly, ulock their site collectios or reattach the databases to the farm to re-eable ed user access for those items. 11. Fially, restart the SharePoit 2010 Timer service o your farm s Cetral Admiistratio site host server. Restorig a SQL Backup to a New SharePoit Eviromet Oe of the great thigs about SharePoit s reliace o its databases is that it makes the data i your SharePoit farm much more maageable ad portable. I steps that are described ext, you ca move or copy a cotet database full of sites from oe SharePoit farm to aother without losig cotet or cofiguratios withi a site. This is especially useful if you wat to move a site collectio from a quality assurace (QA) eviromet to a productio eviromet, or you wat

200 Chapter 7 SQL Server 2008 Backup ad Restore 183 to create a copy of a give site collectio i a ew farm without havig to re-create all of its cotets from scratch. You eed to cosider some prerequisites prior to executig a SQL Server restore of a SharePoit cotet database backup i a ew eviromet: The ew SharePoit farm must already be built. The restore steps i this sectio assume that a ew SharePoit farm has already bee istalled, cofigured, ad is ready to receive the restored cotet database. Patch levels ad versios must be equivalet (or greater). The ew SharePoit farm must be ruig the same versio ad patch level or a more recet versio of SharePoit as the farm that the database backup was created i. If the restore farm is at a more recet versio of SharePoit, the platform updates the database to the correct database schema for the farm s versio automatically. All istalled custom code ad files i the origial farm must be preset i the ew farm. The ew SharePoit farm must have all the same solutios, features, site defiitios, workflows, ad ay other custom code or files istalled ad cofigured as the origial farm. Oly restore cotet databases. This process caot be used to restore a cofiguratio database to a ew farm; cotet databases for oe or more site collectios ca be restored ito a ew farm usig this process, as well as databases associated with Service Applicatios as log as the Service Applicatio for the database has already bee restored or created i the ew farm. Use SharePoit 2010 s Uattached Cotet Database optio if you are restorig a database to its origial farm ad ot overwritig the existig database. Accessig a restored cotet database from its origial farm as a uattached cotet database is the oly way to avoid data itegrity issues ad globally uique idetifier (GUID) coflicts throughout your farm without overwritig the database, eve if you give it a ew ame i SQL Server. For more iformatio o accessig uattached cotet databases i your SharePoit farm, see Chapter 9. To restore a SQL Server database backup of a SharePoit cotet database to a ew farm, execute the followig steps: 1. Restore the database i the SQL Server database istace for the ew farm. If the database does ot previously exist i the istace, you ca create a empty database i the istace ad overwrite it with the backup or type the ame of the ew cotet database ito the To Database field i the Restore Database widow. Do t overwrite existig cotet databases for the ew farm. 2. After you ve restored the database, review its settigs to esure that the target s farm database access service accout is assiged as the database ower. You ca check this i

201 184 SharePoit 2010 Disaster Recovery Guide SQL Maagemet Studio by right-clickig o the database ad choosig Properties. I the Geeral tab, uder the Database sectio, see the Ower property. If it is ot assiged, use the sp_chagedbower <domai/userame4 Trasact-SQL commad to update the database ower ( aspx). Makig the farm database service accout the database ower assigs this accout the DB Ower security role. 3. If there is ot already a Web applicatio i your farm that you wat to associate the site collectio(s) i the restored database with, create oe. Ope the ew farm s Cetral Admiistratio site i a browser, click the Applicatio Maagemet lik, ad the click the Maage Web Applicatios lik i the Web Applicatios sectio of the page. 4. Whe the Applicatio Maagemet page opes, click the New butto i the Web Applicatios sectio of the Cetral Admiistratio site s Fluet user iterface (UI) (also kow as the ribbo). 5. Whe the Create New Web Applicatio widow opes (see Figure 7.17), select the desired cofiguratio settigs for the ew Web applicatio ad click the OK butto to create it. 6. Whe the ew target Web applicatio has bee created to receive the restored cotet database, you ca delete its iitial cotet database because the site cotet you are iterested i resides i the restored cotet database. Retur to the Applicatio Maagemet page i the Cetral Admiistratio site, ad click the Maage Cotet Databases lik i the Databases sectio. 7. Whe the Maage Cotet Databases page opes (see Figure 7.18), if ay cotet databases exist for the Web applicatio, click the liked ame of the cotet database for the Web applicatio to ope its Settigs page. If o cotet databases curretly exist for the Web applicatio, proceed to step 9. Cautio: Be sure to cofirm that the correct Web applicatio is listed i the Web Applicatio drop-dow meu i the upper-right corer of the page. If it is ot, click the arrow for the drop-dow meu ad select the Chage Web Applicatio optio. Whe the dialog box opes, avigate to the correct Web applicatio ad select it. 8. Whe the Maage Cotet Database Settigs page opes (see Figure 7.19), check the Remove Cotet Database check box, which causes a cofirmatio widow to be displayed (see Figure 7.20) if the cotet database cotais existig site collectios. If the cofirmatio widow is displayed, determie whether you ca remove the cotet database from the farm. If you ca, click the OK butto i the cofirmatio widow ad click the OK butto to remove the cotet database.

202 Chapter 7 SQL Server 2008 Backup ad Restore 185 Figure 7.17 The SharePoit Cetral Admiistratio site s Create New Web Applicatio widow. Figure 7.18 The Maage Cotet Databases page.

203 186 SharePoit 2010 Disaster Recovery Guide Figure 7.19 The Maage Cotet Database Settigs page. Figure 7.20 The cofirmatio widow displayed whe a user clicks the Remove Cotet Database check box warig him of the implicatios of the actio. 9. After all cotet databases have bee removed from the Web applicatio, retur to the Maage Cotet Databases page for the target Web applicatio ad click the Add Cotet Database butto i the upper-left corer of the page. 10. I the Add Cotet Database page (see Figure 7.21), eter the ame of the database istace hostig the restored cotet database i the Database Server field ad the ame of the restored cotet database i the Database Name field. Cofirm the other settigs for the cotet database, ad click the OK butto to add the database. Note: If you are more comfortable usig PowerShell, see Chapter 10 for iformatio o how to add the restored cotet database to your ew farm with it.

204 Chapter 7 SQL Server 2008 Backup ad Restore 187 Figure 7.21 The Add Cotet Database page. 11. After the cotet database has bee added to the Web applicatio, review the cotets of the database through SharePoit to cofirm that the additio of the database was successful. View the Web applicatio s ew site collectio(s) through the Cetral Admiistratio site to cofirm that they are properly listed, ad ope them directly through a browser to verify that all their cotets ad settigs were correctly restored ito the ew eviromet. Tip: You may eed to reset the Iteret Iformatio Services (IIS) Web servers hostig your ew farm for these chages to be visible to ed users. Coclusio Like SharePoit, Microsoft provides several optios for backig up ad restorig your SQL Server databases to meet the specific eeds of your orgaizatio. The procedures discussed i this chapter merely scratch the surface of what is possible with SQL Server s backup ad restore optios, ad the advet of a ew versio of SQL Server brigs with it eve more opportuities for esurig the security ad log-term viability of your busiess-critical data. Noe of this takes ito accout the third-party tools available to ehace, exted, or replace SQL Server s backup ad restore tools. (For a itroductio to some of these tools, see Appedix B, Third-Party

205 188 SharePoit 2010 Disaster Recovery Guide Tools, available o the Cegage Learig Web site at With the iformatio i this chapter, you should be able to start compilig a backup ad restore strategy for your databases, selectig the cofiguratio ad procedures that best suit the eeds of your orgaizatio ad ifrastructure. Keep i mid that although backig up your SharePoit databases is a good start o preparig your SharePoit farm for the possibility of a catastrophic evet, that s all it is: a start. How SharePoit relies o ad uses its databases is far from ormal ad, as you have see, this meas you must make special cosideratios ad plas whe backig up ad restorig those databases. Agai, like SharePoit, usig SQL Server s tools to back up ad restore your Share- Poit database is ulikely to be a complete disaster recovery solutio for your orgaizatio. Makig that assumptio leaves you vulerable ad most likely uable to quickly recover your system i the evet of a disaster, if at all. Restorig a backup ca be a time-itesive process ad ca cost your eterprise coutless ma-hours of lost productivity as your users wait for Share- Poit to be brought back olie. Thakfully, backup ad restore is ot the oly method available with SQL Server for restorig ad, just as importatly, maitaiig service to your farm s databases. Chapter 8, SQL Server 2008 High Availability, itroduces you to the cocept of high availability (HA) ad some of the paths you ca take to help your SQL Server eviromet withstad a outage or disaster. These practices are ivaluable to your busiess, because they are iteded to miimize the duratio of a outage as much as possible so your SharePoit farm ca remai available to your ed users. SQL Server backup ad restore ca be a powerful asset i your SharePoit disaster recovery toolkit, but as has bee show with so may of the other tools you have at your disposal, it does ot ecessarily stad well o its ow for SharePoit. As you cotiue through this book, start to thik about how you wat to put together all this iformatio to costruct your ow SharePoit disaster recovery solutio. You are ot quite fiished learig the various tools ad platforms you eed to cosider, but you are gettig there. After readig this chapter, you should be able to cofidetly aswer the followig questios about SQL Server s backup ad restore tools: 1. What is the differece betwee a database backed up usig the Full recovery model ad oe backed up with the Simple recovery model? 2. What types of storage media ca you use to store SQL Server database backups? 3. What SharePoit databases should ot be backed up with SQL Server? Why? 4. What are the performace implicatios for your SharePoit farm whe backig up ad restorig large SharePoit databases? 5. What state ca a database be placed i whe it is restored to a SQL Server database istace?

206 8 SQL Server 2008 High Availability I This Chapter Log Shippig Database Mirrorig Database Clusterig High availability (HA) is a term that we covered for compoets of SharePoit 2010 ad the Widows Server operatig system i Chapter 6, Widows Server 2008 High Availability, but there is aother itegral part of SharePoit 2010 s ecosystem that has the ability to be highly available: its SQL Server databases. Because SharePoit is so depedet o the availability of its databases to serve cotet to its users, a good case ca be made that your SQL Server database istace(s) should be the first area of your farm that you review whe plaig for HA. Microsoft has wisely recogized the importace of makig SQL Server highly available ad provides several optios ad tools to assist i that edeavor. I additio, several third-party tools are available that you ca use to support your SQL Server HA cofiguratio ad executio. The first step you must take i plaig ad desigig your SQL Server HA architecture is to evaluate your eviromet s HA requiremets ad available budget. SQL Server HA ca have a high cost associated with it, which you must cosider whe determiig exactly how to implemet it ad establish the amout of uptime you are expected to provide for your SharePoit eviromet. Three built-i optios are available for SQL Server HA (depedig o the type of SQL Server licese i use): log shippig, database mirrorig, ad clusterig. Each of these optios ca be a viable solutio for your SharePoit eviromet, but determiig which oe best fits the eeds ad limitatios of your orgaizatio ad eviromet is a importat activity that you eed to be sure to iclude early i your SharePoit desig process. After all, your decisio has lastig implicatios ad is ot easily chaged without affectig SharePoit. This is yet aother item for discussio that you should cover with your database admiistrator. Your admiistrator s isights ad expertise are ivaluable for ot oly selectig a HA solutio but also implemetig it ad supportig it over time. 189

207 190 SharePoit 2010 Disaster Recovery Guide Note: Each of these HA solutios may require the purchase of additioal Widows Server, SharePoit, ad SQL Server liceses ad hardware to implemet, addig defiitive costs to your eviromet, regardless of what liceses or hardware approach you decide to take. Microsoft states that passive SQL Server istallatios cofigured for HA do ot require additioal liceses uless they process queries. You should cotact your Microsoft licesig or sales resources for specific iformatio about how to properly licese your HA resources. You may also be able to leverage virtualizatio products from Microsoft or VMware to reduce hardware costs by creatig multiple virtual servers o a sigle physical host, but you must carefully evaluate the performace ad support implicatios of this optio. Furthermore, these solutios ca ivolve the use of separate dataceters to host the servers used to make SQL Server highly available, allowig your SharePoit databases to keep servig cotet because they ca fail over to servers i a completely differet geographic locatio. Although this ca be valuable, it adds ifrastructure costs ad solutio complexity ad ca itroduce the potetial for latecy as data is trasferred betwee the dataceters. The visual examples provided i this chapter were geerated i a testig eviromet usig the followig platforms ad compoets. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 Developer Editio with Service Pack (SP) 1 (build ) Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 SharePoit. SharePoit Foudatio 2010 Release Cadidate 1 (build 4730) Log Shippig Origially itroduced as a supported feature with SQL Server 2005, log shippig is a available HA feature i every SQL Server editio except Express. Log shippig takes advatage of the platform s backup fuctioality that was covered i Chapter 7, SQL Server 2008 Backup ad Restore ad uses it to create a secod iteratio of the target (or primary) database i a separate database istace. It creates a secodary copy of the primary database by takig a trasactio log backup from the primary database ad copyig it to a secodary database. The trasactio log copy process eeds to occur regularly to keep the secodary database sychroized with its primary source i case a disaster occurs ad it is eeded. Oe advatage of log shippig is that oce the backup of the trasactio log is created i the primary database istace, the remaider of the process occurs i the secodary database istace, allowig the primary istace to retur to ormal activities.

208 Chapter 8 SQL Server 2008 High Availability 191 The Server Compoets of Log Shippig Log shippig requires at least two servers a primary ad a secodary ad allows the use of a optioal third server to moitor the log-shippig operatio. Primary. This is the database you wat to back up to a SQL Server istace o a separate server. All cofiguratio of the log-shippig process must occur o this server. You must back up the primary database usig the Full or Bulk-Logged recovery models for the backups to be used with log shippig; log shippig is ot available whe the target database uses the Simple recovery model. A target database ca have oly oe primary server, but you ca ship its logs to multiple secodary servers for redudacy. Secodary. This is the database that fuctios as a separate backup copy of your primary database. You must iitially restore the secodary database from a full backup of the primary database usig either the Restore with No Recovery or Restore with Stadby optios before you ca update it with trasactio logs via log shippig. A sigle secodary server ca host multiple databases backed up via log shippig. Moitor. This server lives up to its ame by trackig all the activities of the log-shippig process, such as trasactio log backup dates, secodary server trasactio log copy ad restore dates, ad iformatio o ay failures or errors that may occur. A moitor server is ot required to use log shippig, but if you do decide to use it, you should host it somewhere other tha your primary or secodary server. A sigle moitor server ca track multiple logshippig cofiguratios. Log-Shippig Jobs SQL Server executes four distict SQL Server Aget jobs as part of the log-shippig process: Backup. The SQL Server Aget executes this job o the primary server to back up the target database, log the actio to the local server (as well as the moitor server), ad clea up ay old backup files or logs created by previous iteratios of the job. This job kicks off the logshippig process; whe it is fiished, SQL Server iitiates a Copy job o the secodary server ad returs the target database to ormal processig. By default, Backup is cofigured to ru every 2 miutes, but you ca cofigure it to ru more or less frequetly based o your requiremets. Copy. The SQL Server Aget executes this job o the secodary server to copy the trasactio log backup from the primary server to the secodary server. Its actios are logged o the secodary server ad reported to the moitor server, ad the it deletes ay old backup files or logs. A Warig About the Size of Your Trasactio Log Files Be careful to moitor the size of ay database ad its trasactio logs if you are usig log shippig. As these files grow, so does the amout of data that you eed to sed over the etwork from your primary server

209 192 SharePoit 2010 Disaster Recovery Guide to the secodary server. The larger the trasactio log, the loger it takes for it to be copied from the primary to the secodary ad the more badwidth that is beig tied up over your etwork. The good ews is that solutios are available to make the trasfer of large log files more efficiet ad better performig. Compressig trasactio log backups, a feature ow available i SQL Server 2008 (see Chapter 7 for more iformatio o SQL Server 2008 s backup compressio), ca reduce the size of the files that are set over the etwork. Other methods are also available to improve the act of copyig the files from poit A to poit B, such as the Widows Distributed File System with Active Directory Domai Services, which ca icrease the throughput of the copy activity. Restore. The SQL Server Aget executes this job to restore the copied trasactio log to the secodary database ad brig it i lie with the cotet of the primary target database. Its actios are logged o the secodary server ad reported to the moitor server; the it deletes ay old files or logs associated with the job. Alert. If a moitor server is cofigured for the log-shippig process, this job is created o the moitor server ad shared by all servers usig the moitor server. The SQL Server Aget executes this job to raise alerts whe ay job withi the log-shippig process fails to ru successfully to completio. Additioal cofiguratio must be completed for SQL Server to deliver these alerts to a operator. If a moitor is ot cofigured, alert jobs must be cofigured idividually o the primary ad secodary servers to report the result of the jobs ru o each server. How to Cofigure Log Shippig Your eviromet must meet the followig requiremets to eable log shippig for oe or more of your SQL Server databases: Servers. I additio to the server hostig your primary SQL Server database istace, you must have a secod database istace hostig o a separate server to fuctio as the secodary server. A third moitor server is optioal. File share. A etwork file share must be available to store the backed up trasactio logs. Microsoft recommeds, but does ot require, that this file share be located somewhere other tha your primary or secodary server i the iterest of ehaced availability for your data. SQL Server licese. All servers participatig i the log-shippig process must be ruig oe of the followig versios of SQL Server: Server 2008 or 2008 R2 Workgroup Editio, Server 2008 or 2008 R2 Web Editio, SQL Server 2008 or 2008 R2 Stadard Editio, SQL Server 2008 or 2008 R2 Dataceter Editio, or SQL Server 2008 or 2008 R2 Eterprise Editio. Log shippig is ot available with SQL Server Express Editio.

210 Chapter 8 SQL Server 2008 High Availability 193 Case sesitivity. All servers participatig i the log-shippig process must have the same SQL Server case sesitivity cofiguratio. Recovery model. You must back up the database targeted for log shippig usig the Full or Bulk-Logged recovery models. SQL Server Aget. The SQL Server aget service must be ruig o each server for the associated jobs to execute. I most cases this service is active by default, but if it is ot ruig, the log-shippig process is ot fully fuctioal. The followig steps provide a example of how to eable ad cofigure SQL Server log shippig with a primary ad secodary server: 1. Ope SQL Server Maagemet Studio ad right-click o the database you are targetig for log shippig. Select the Properties item from the meu. 2. Whe the Database Properties dialog box opes (see Figure 8.1), click the Trasactio Log Shippig lik i the left pae. Figure 8.1 The Geeral page of the Database Properties dialog box for a selected database i SQL Server Maagemet Studio.

211 194 SharePoit 2010 Disaster Recovery Guide Figure 8.2 The Trasactio Log Shippig page of the Database Properties dialog box. 3. This actio opes the Trasactio Log Shippig page (see Figure 8.2) with most of its optios disabled. Click the Eable This as a Primary Database i a Log Shippig Cofiguratio check box to eable the other fields, buttos, ad items i the page. 4. To ope the Trasactio Log Backup Settigs dialog box (see Figure 8.3), click the ow eabled Backup Settigs butto. 5. I the Network Path to Backup Folder text box, eter the Uiversal Namig Covetio (UNC) path for the etwork share you have desigated as the storage locatio for the backed up trasactio logs. If you have chose to use a local folder o the primary server, leave this field blak ad eter the path to that directory i the If the Backup Folder Is Located o the Primary Server, Type a Local Path to the Folder text box.

212 Chapter 8 SQL Server 2008 High Availability 195 Figure 8.3 The Trasactio Log Backup Settigs widow allows you to set the storage locatio of the trasactio log backups, maage the deletio schedule for those backups, ad set operator alerts i the case of errors. Note: Regardless of its locatio, the primary server s SQL Server service accout must have read ad write privileges for the directory provided. I additio, the secodary server s SQL Server Aget service accout must have read privileges i the directory. 6. Cofigure the Delete Files Older Tha ad Alert if No Backup Occurs Withi fields accordig to the eeds ad requiremets of your system. The first field helps to keep your trasactio log backups from overwhelmig your storage system, whereas the secod wars your database s operators if its trasactio logs are ot beig backed up o a regular basis.

213 196 SharePoit 2010 Disaster Recovery Guide Figure 8.4 The Job Schedule Properties widow. Tip: Be careful ot to set too small of a iterval o the deletio of your backup files, or they may be deleted before the log-shippig Copy job ca create a copy of the files o the secodary server. 7. I the Backup Job sectio, you have the optio of reamig the job used to back up the target database if the default ame provided is ot sufficietly descriptive. More importatly, clickig the Schedule butto opes the Job Schedule Properties dialog box (see Figure 8.4), allowig you to cofigure how frequetly the database s trasactio logs are backed up ad set to the secodary server. You ca modify the various schedule settigs for the backup i this widow; be sure to closely review the Summary text field to cofirm that the settigs match your preferred schedule before clickig the OK butto to save your chages.

214 Chapter 8 SQL Server 2008 High Availability 197 Tip: As with ay other scheduled activity withi your farm, such as SharePoit backups, search crawls, or other regular activities, be careful about whe you decide to have the trasactio logs backed up ad shipped to the secodary server. These processes could icur some (if ot cosiderable) overhead for your eviromet ad have the potetial to impact the experiece for your ed users, especially if there are other resource-itesive activities ruig at the same time. It may be difficult, but at a miimum you eed to be aware of the possibility for cotetio with these ad other scheduled activities. 8. To save your chages to the Trasactio Logs Backup Settigs, click the OK butto. This returs you to the Trasactio Log Shippig page of the database s Properties widow. 9. Now that you have cofigured the backup of the primary database s trasactio logs, click the Add butto i the Secodary Databases sectio to select a secodary server to receive the backed up logs. Note: You must eter a storage locatio for the trasactio log s backups i step 5 for the Add butto to be eabled. 10. This opes the Secodary Database Settigs dialog box (see Figure 8.5). By default, most of the items are disabled whe this dialog box first opes; you must coect to the secodary server to be able to modify them. Click the Coect butto to ope a SQL Server logi scree, ad eter the coectio data for the secodary server s database istace to proceed. 11. The Iitialize Secodary Database tab is ow eabled, allowig you to select whether you wat the secodary database iitialized by a fresh full database created by the logshippig process, by a existig full backup that has already bee take, or to iform SQL Server that the database has already bee iitialized. Select the optio butto ext to the correct optio for your system, cofigure ay ecessary Restore Optios, ad the click the Copy Files tab. 12. I the Copy Files tab (see Figure 8.6), you must provide a destiatio directory o the secodary server for the trasactio log backup files copied from the primary server. (The widow s OK butto is ot eabled util you eter a value i this field.) You ca also cofigure how log these log files are retaied, whe operators should be alerted i case of a outage, ad the schedule by which the log files are copied from the primary server to the secodary server. After you have completed the Copy Files cofiguratio, click the Restore Trasactio Log tab to cotiue.

215 198 SharePoit 2010 Disaster Recovery Guide Figure 8.5 The Secodary Database Settigs dialog box prior to coectio to the secodary server. Tip: The schedule for copyig files to the secodary server should match the schedule for trasactio log backups as closely as possible. Copyig the files with a greater frequecy ca result i the same data beig copied multiple times, whereas a lesser frequecy ca result i the loss of trasactio data if backups are overwritte or deleted before they ca be copied. 13. I the Restore Trasactio Log tab (see Figure 8.7), you must select the state that the database is i while restorig backups. The No Recovery Mode optio is selected by default, but you ca also opt to place the database i Stadby Mode. The tab also allows you to delay a restore, alert a operator if a restore caot be ru, ad chage the schedule for restore operatios. 14. After you have completed your Secodary Database Settigs cofiguratios, click the OK butto to retur to the Database Properties dialog box.

216 Chapter 8 SQL Server 2008 High Availability 199 Figure 8.6 The Copy Files tab of the Secodary Database Settigs dialog box. 15. If you wat to cofigure a moitor server for the log-shippig process, select the Use a Moitor Server Istace check box i the Moitor Server Istace sectio. This eables the Settigs butto i that sectio; click it to ope the Log Shippig Moitor Settigs dialog box (see Figure 8.8.). 16. Whe the Log Shippig Moitor Settigs dialog box opes, click the Coect butto to ope a SQL Server logi scree ad eter the coectio data for the moitor server s database istace to proceed. I this dialog box, you ca also cofigure which accout is used to coect to the moitor server, how log the moitor server retais history data, ad whe alert jobs are scheduled to ru. After you have completed your cofiguratio, click the OK butto to retur to the Database Properties dialog box. 17. After you have completed the log-shippig cofiguratio for the database, click the OK butto i the Database Properties dialog box to commit your chages.

217 200 SharePoit 2010 Disaster Recovery Guide Figure 8.7 The Restore Trasactio Log tab of the Secodary Database Settigs widow. 18. To verify that the log-shippig cofiguratio was completed successfully, review the status of the SQL Aget jobs o each server ad cofirm that they are ruig as expected ad without error. SharePoit ad Log Shippig As with SQL Server database backups i geeral, several types of SharePoit databases caot be preserved via SQL Server log shippig. The followig list addresses each type of database ad whether it ca be made highly available via trasactio log shippig. Cofiguratio database. You should ot log-ship SharePoit cofiguratio databases; cofiguratio databases are farm specific. A cofiguratio database is iteded to be used oly with the origial farm it is attached to. Search databases. Because search databases are tightly itegrated with the idex files stored o the file system of a SharePoit crawl server, you should ot log-ship them. The time it takes to trasfer log files betwee primary ad secodary servers ca result i icosistecies

218 Chapter 8 SQL Server 2008 High Availability 201 Figure 8.8 The Log Shippig Moitor Settigs dialog box. betwee the database ad the idices. I the case of a disaster, it is likely a better optio to re-create the idices from scratch or back them up usig the Cetral Admiistratio site or PowerShell tha a SQL Server backup. If the SharePoit cotet databases that are beig log-shipped are attached to a stadby farm, you ca use that farm s search compoets to crawl ad idex them. Some Service Applicatio databases. It is difficult to succictly idetity exactly what databases for SharePoit 2010 Service Applicatios caot be log-shipped because of the large umber of Service Applicatios available as well as the fact that the Service Applicatio Framework is extesible ad supports the creatio of custom Service Applicatios. For a good list of what Service Applicatio databases ca ad caot be log-shipped, as well as geeral criteria for makig the distictio, see ff aspx. Also, review ay documetatio available for each Service Applicatio to determie its specific availability for log shippig or lack thereof.

219 202 SharePoit 2010 Disaster Recovery Guide Cotet databases. You ca log-ship SharePoit cotet databases to a secodary server. You ca also attach them to a stadby SharePoit farm for limited read-oly viewig, if you restore them i Restore i Stadby mode. Depedig o how the stadby farm is set up, some fuctios such as search, user profiles, ad people search may ot be available without some extra cofiguratio efforts. As you ca see i the list, ot every type of SharePoit database is highly available through SQL Server log shippig. This directly iflueces how you should use log shippig to implemet HA for your SharePoit farm s databases, because you ca t simply switch over to your secodary log-shipped databases if your primary databases are lost. You ca take two approaches whe usig SQL Server log shippig with SharePoit: creatig stadaloe secodary cloes of your Service Applicatio ad cotet databases or creatig a full stadby SharePoit farm based o your log-shipped Service Applicatio ad cotet databases. Because you caot make your cofiguratio ad search databases highly available via log shippig, you must build a ew farm to host the log-shipped Service Applicatio ad cotet databases to restore your eviromet to its users. The first optio meas that you are ot goig to build a ew farm util a disaster occurs, but it does reduce your startup time because the cotet is preserved i a separate database host ad ready to be reitroduced back ito the farm. If a outage hits a sigle database, it gives you a ruig resource to add back ito your farm. The fact that this optio takes more time to use i a recovery sceario does the require that you have greater leeway i terms of your recovery time objective (RTO) for your SharePoit farm. The secod optio allows you to have a full, upto-date replacemet available for your farm i the case of a catastrophic evet, shorteig the time that your eviromet is uavailable to your users ad allowig you to meet a much smaller RTO widow. Although the specifics of implemetig the first optio have already bee covered i the chapter, you eed to take additioal steps to create a full stadby SharePoit farm usig log-shipped databases. Buildig a stadby SharePoit farm provides a system for the log-shipped Service Applicatio ad cotet databases to be itegrated ito ad gives you a fallback optio if a disastrous evet should befall your primary productio SharePoit farm. It also gives you a read-oly eviromet where users ca view data or ru reports without impactig the performace of your productio farm. (Keep i mid that this may ifluece how the platforms i your stadby farm are licesed.) You ca use the followig steps as a guide to build your ow stadby Share- Poit farm. 1. Cofigure log shippig for each database selected to be replicated ito the stadby farm usig the Restore to Stadby mode. 2. Istall SharePoit i the stadby farm, usig the SQL Server database istace hostig the log-shipped databases as the database host for the stadby farm.

220 Chapter 8 SQL Server 2008 High Availability 203 Note: If possible, use PowerShell (you ca also use VBscript or aother compatible scriptig laguage, but others are ot as powerful as PowerShell, if you get our drift) to script the istallatio ad cofiguratio of both your primary ad stadby SharePoit farms. This gives you a much higher probability of creatig idetical deploymets i both eviromets, which i tur gives you a higher probability of success for your logshippig cofiguratio. I geeral, take special care to apply the same patches, hotfixes, or updates to the operatig systems, SharePoit, ad SQL Server i the stadby farm as have bee applied to your productio farm. You must build the stadby farm to the same SharePoit versio as your productio farm. If your productio farm has ay custom code or laguage packs istalled, also istall them to the stadby farm. 3. Cofigure the stadby farm to match the setup of the productio farm. (SharePoit 2010 s ew cofiguratio-oly backup ad restore fuctioality may be helpful here; see Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore ad Chapter 10, SharePoit 2010 Commad Lie Backup ad Restore: PowerShell for more iformatio.) If you have a Service Applicatio cofigured i your productio farm, you must either create a ew Service Applicatio to match it or restore a backup of the Service Applicatio from the productio farm ito the stadby farm so you ca be certai that the cofiguratio matches exactly. (See the previously refereced documet o Microsoft s TechNet Web site for iformatio o how to cofigure specific Service Applicatios, as well as the product documet for the Service Applicatio itself.) Although you should coduct a search i the stadby farm, disable ay search crawls uless you specifically eed them. Cofirm that the stadby farm s MySite cofiguratio matches that of the productio farm s. 4. To build the ew stadby Web applicatios for each Web applicatio i your productio farm, execute steps 2 through 11 from the list i the Restorig a SQL Backup to a New SharePoit Eviromet sectio i Chapter 7, addig the log-shipped cotet databases to each ew Web applicatio. 5. I the stadby farm, cofigure a alterate access mappig (AAM) that poits to the URL of your productio farm; see Figure 8.9 for a example of the Add Iteral URLs page. 6. O the file system of all the Web frot-ed (WFE) servers i the stadby farm, ope the server s Hosts file (typically located at %WINDIR%\system32\drivers\etc\). See Figure 8.10 for a example. The add a etry poitig the productio farm s URL at the server s local loopback IP address, This esures that ay requests for the productio farm that origiate o the local server are directed back to the local server, ot a server i your productio farm.

221 204 SharePoit 2010 Disaster Recovery Guide Figure 8.9 The Add Iteral URLs page i the SharePoit Cetral Admiistratio site. Figure 8.10 A example of the Hosts file o a Widows server. 7. If you are usig SharePoit Server 2010, Search Server 2010, or Search Server 2010 Express, i the stadby farm ope the Search cotet source amed Local Office Server SharePoit Sites for editig. Remove ay URLs that refer to local servers i the stadby farm or the URL of the stadby farm, ad replace them with the URL of the productio farm.

222 Chapter 8 SQL Server 2008 High Availability 205 Tip: Uless you have a specific eed to make search queries i the stadby farm, try to esure that o crawls are scheduled to ru i the farm util it is eeded i the case of a failover. This reduces the resources that the stadby eviromet uses ad makes it easier to cofigure search for the proper targets should a failover occur. 8. Your stadby farm is ow ready to be used as a read-oly copy of your productio farm that ca be failed over to i case of a outage or disaster. Cautio: Oce your stadby farm is created, be careful to duplicate every cofiguratio chage or update that you make to your primary SharePoit farm to your stadby farm. If the two eviromets are ot kept i syc, you risk displayig icosistet cotet to your users or worse, breakig your stadby farm etirely whe it attempts to use your modified Service Applicatio ad cotet databases that are log-shipped ito it. Although usig SQL Server log shippig as your HA solutio has several beefits, it also has quite a few drawbacks that you must cosider whe evaluatig the approach. This is ot to say that log shippig is or is ot a good solutio. Our mai cautio is that you pay close attetio to the items that follow ad determie how they relate to your eviromet, eeds, ad limitatios. You may fid that log shippig fits you like a glove, or you may fid that oe of the other HA solutios i this chapter is what you eed to brig log-term stability to your database eviromet. Log-Shippig Pros Log shippig may be the right HA solutio for your eviromet for a variety of reasos. The followig list outlies its positive attributes. Take a look to see if it meets your eeds. Idepedece. The jobs used to log-ship a database are ot tied to SharePoit, or are they impacted by ay other processes i the SQL Server database istace. This meas that chages to your SharePoit cofiguratio or its databases do ot directly impact or harm your log-shippig procedures. Cost effectiveess. Ulike some other HA solutios (such as clusterig), log shippig does ot require high-priced compoets ad (as oted earlier) ca be implemeted for the costs that may or may ot be associated with provisioig ad licesig a additioal SQL Server istace. Highly cofigurable ature. As described earlier, a large umber of optios ad cofiguratios to be set for log shippig allow it to meet the eeds of your eviromet. Read-oly availability. If you wat, you ca create a read-oly versio of your SharePoit eviromet usig its log-shipped cotet databases for research or reportig purposes to reduce the load placed o your primary farm.

223 206 SharePoit 2010 Disaster Recovery Guide Low impact o performace. Oce the trasactio logs of your SharePoit database are backed up, the log-shippig process is executed o the server(s) hostig the secodary database ad has o affect o the performace of your primary database server. Ulimited use. You ca log-ship as may databases i a istace as you wat; the platform imposes o hard limit. (Keep i mid that you may still ecouter limits imposed by the capacity of your hardware or etwork ifrastructure.) Use of backups. The trasactio log backups that the log-shippig process uses to update the secodary database ca restore the primary database to a previous poit i time as ecessary. This meas that you ca make your database highly available ad implemet a backup/ restore solutio for it at the same time, a optio ot available with SQL Server s other HA solutios. I this situatio, it is still ecessary to perform full backups of your trasactio logs over time, otherwise restore operatios are goig to take much loger to implemet all of the differetial backups back to the origial full backup, but completely feasible. Capture completeess. Because SQL Server records iformatio about a database update to the database s trasactio log before it eve writes it to the database, all the requested database modificatios received by SQL Server leadig up to the momet of a outage are copied over to the secodary server ad writte to that database. Distributio ad redudacy. By requirig a secodary database istace to host your secodary database, log shippig makes your system more highly available by providig fallback optios for your primary database server. The ability to ship database logs to multiple secodary database istaces meas that you ca further limit your risk by icreasig the umber of fallback optios you have available. Geographic redudacy. Log shippig does ot face the distace limitatios that come with database mirrorig or failover clusterig, allowig copies of your databases to be distributed to remote locatios for true redudat protectio of your data from large-scale disasters. FILESTREAM compatibility. SharePoit databases cofigured to use SQL Server s FILE- STREAM provider for Remote Biary Large Object (BLOB) Storage (RBS) ca be logshipped to a stadby database istace for preservatio. You ca log-ship other third-party RBS providers if the provider supports it. Log-Shippig Cos As with most techology solutios, log shippig i SQL Server 2008 is ot a perfect solutio. Review the followig list to see where it falls short ad how that might affect your SharePoit eviromet. Maual failover. Out of the box, SQL Server does ot automatically fail a system over to the log-shipped secodary database if the primary database goes dow. Although it is true that log shippig does have a third server role the moitor role that role oly tracks the status

224 Chapter 8 SQL Server 2008 High Availability 207 of log-shippig operatios; it caot make the log-shippig database istace a primary if somethig happes to the origial primary istace. You ca do additioal cofiguratio to automate this process, but by default you must maually switch over to the log-shipped databases. This ca impact the time it takes to restore your system after a outage, depedig o how quickly your IT staff is otified of the outage ad what availability they have to restore the system to the log-shipped databases. Latecy. Updates are ot immediately copied to the secodary database whe they are made i the primary database. Several factors ca affect the time it takes for them to make it over to the secodary database, icludig these: the frequecy with which your trasactio logs are backed up, the size of those logs, ad the badwidth available betwee the primary ad secodary databases. The data i your secodary database is ot goig to be up to date util the trasactio logs are copied to it ad restored, which ca impact the cotet of a stadby farm. Because log shippig does ot update i real-time, you caot use it to restore a database to the poit i time immediately prior to a failure. If your orgaizatio s recovery poit objective (RPO) ad RTO requiremets for SharePoit madate istataeous failover with o lost trasactios or data, log shippig is ot a viable HA solutio for your SQL Server eviromet. Poor status visibility. Although the log-shippig process geerates status reports for all its actios ad allows for the cofiguratio of a moitorig server, this iformatio is ot goig to be easily available. You ca access these reports oly by loggig o to the server where they are stored; the reports oly raise alerts to operators of the associated SQL Server istaces whe they log ito the istaces. Additioal custom measures or the use of a moitorig platform such as the Operatios Maager platform from Microsoft is goig to be required to make this iformatio available to your SharePoit admiistrators or to automatically deliver the alerts as they occur without requirig admiistrators to log ito a system. Not a complete solutio. As previously metioed, you are ot able to log-ship all your SharePoit databases, requirig additioal steps such as buildig a whole ew farm or creatig a stadby farm to use the log-shipped databases i the case of a disaster. Errors ad data loss. Ay errors that are writte to your primary databases are also trasferred to your secodary databases via log shippig. Log shippig is ot to prevet the loss of data due to accidetal deletio; if it is deleted i the primary database, it is also deleted i the secodary database oce the trasactio is log-shipped over. If the features ad fuctioality of log shippig i SQL Server 2008 seem appealig but you still have cocers about some or all of the drawbacks to the process, have o fear. There are, however, other alteratives whe it comes to HA for SQL Server, ad the ext oe o the list, database mirrorig, offers several ehacemets to log-shippig s feature set while also improvig o its weakesses. (Keep i mid that database mirrorig comes with its ow set of weakesses ad drawbacks.) Although the two optios are similar, there are defiitely some differeces betwee

225 208 SharePoit 2010 Disaster Recovery Guide the two, especially whe it comes to the icreased cost of implemetig database mirrorig. I additio, you ca implemet both log shippig ad database mirrorig for your SharePoit eviromet, givig you the best of both worlds. This is t to say that log shippig is ecessarily iferior to the other HA solutios available for SQL Server: database mirrorig or failover clusterig. Microsoft has desiged these solutios to offer you a rage of flexible ad cofigurable optios to meet your eviromet s specific eeds, ad log-shippig ca play a importat role i your disaster recovery desig. Log shippig allows you to meet shorter RTOs tha ormal SQL Server backups, because you already have a copy of your databases up ad ruig i a SQL Server eviromet, at a much lower cost tha mirrorig or clusterig thaks to its less expesive ifrastructure requiremets. Log shippig also eables you to provide broader protectio of your eviromet, because logs ca be shipped to multiple locatios ad to diverse geographic locatios. Fially, log shippig is attractive because you ca use it with a much broader rage of SQL Server fuctioality, such as RBS. Database Mirrorig SQL Server s database mirrorig fuctioality is similar to log shippig i the way it maitais a copy of the primary database for HA purposes; both approaches copy trasactio log data from the primary to the secodary database. Although the similarities betwee the two HA solutios for SQL Server may be strikig, the differeces betwee them are eve more so. Database mirrorig differs from log shippig i several areas, the three most apparet beig whe the trasactio log data is copied to the secodary server, how that data is trasferred from oe server to aother, ad how the databases behave whe the primary server suffers a outage. Database mirrorig s most appealig advatage over log shippig is that trasactios committed to the primary database are copied over to the secodary database istace at oce after they are writte to the database. This gives database mirrorig a distict advatage over log shippig by reducig latecy ad esurig that the cotets of the secodary database are completely curret. Whe the trasactios are set to the secodary database, the idividual trasactio records are set to the secodary database via TCP, ot trasactio log backups via a file system copy. But the most desirable aspect of database mirrorig is that you ca cofigure it to automatically fail over to the secodary server should the primary server suffer a outage. That s a big chage from log-shippig s reliace o a maual failover. Tip: If the etwork beig used to sed the trasactio records is ot secure, take precautios to secure ad ecrypt the database mirrorig traffic as it is set. For specific iformatio o this subject, Microsoft has published a article o database mirrorig trasport security at

226 Chapter 8 SQL Server 2008 High Availability 209 The Server Compoets of Database Mirrorig Database mirrorig requires at least two servers a pricipal ad a mirror ad allows the use of a optioal third server, a witess, to automate failovers from the pricipal to the mirror i the case of a outage o the pricipal. Pricipal. This is the database you wat to mirror to a SQL Server istace o a separate server. You must back up the pricipal database usig the Full recovery model for the database to use database mirrorig; mirrorig is ot available whe usig the Simple or Bulk-Logged recovery models. There ca be oly oe pricipal server for a target database, ad it ca have oly oe mirror server as a parter i the mirrorig sessio. You ca implemet this role o servers usig the Eterprise or Stadard liceses for SQL Server. Mirror. This is the database that fuctios as the mirrorig parter for your pricipal database. You must iitially restore the mirror database from a full backup of the pricipal database usig the Restore with No Recovery optio (ad the ay trasactio log backups required to make the database up to date) before you ca update it with trasactios via database mirrorig. See Figure 8.11 for a example of where this settig is selected. See the How to Restore a SQL Server 2008 Database Backup sectio of Chapter 7 for more iformatio o how to restore a database i the SQL Server Maagemet Studio. A sigle secodary server ca host multiple databases actig as mirrors to pricipal databases o other servers. Databases hosted o the mirror istace ot actig as a mirror ca also be pricipal databases i database mirrorig with other database istaces. You ca implemet this role o servers usig the Eterprise or Stadard liceses for SQL Server. Witess. This server is optioal ad is eeded oly if you require SQL Server to automatically fail over to the mirror database if a failure or outage occurs o the pricipal database. The witess server does ot perform resource-itesive activities or host cotet as part of the database mirrorig process; its oly role is to detect a failure i the pricipal database ad eable automatic failover to the mirror. You ca implemet this role o servers usig the Eterprise, Stadard, Workgroup, or Express Editio liceses for SQL Server. Cautio: Microsoft does ot support mirrorig cofiguratios where databases from the same pricipal database istace are copied to mirrors i separate database istaces. Wheever possible, you should strive to mirror all the databases i a pricipal istace to a sigle mirror istace.

227 210 SharePoit 2010 Disaster Recovery Guide Figure 8.11 The Optios page of the Restore Database dialog box with the Restore with No Recovery radio butto highlighted. How to Cofigure Database Mirrorig Your eviromet must meet the followig requiremets to eable database mirrorig for oe or more of your SQL Server databases: Servers. I additio to the server hostig your pricipal SQL Server database istace, you must have a secod database istace hostig o a separate server to fuctio as the mirror server. A witess server is optioal but is required if you wat to have automatic failover. SQL Server licese. The pricipal ad mirror servers must be ruig oe of the followig versios of SQL Server: SQL Server 2008 or 2008 R2 Stadard Editio (sychroous mirrorig oly; the various modes of database mirrorig available are discussed later i this sectio), or SQL Server 2008 or 2008 R2 Eterprise Editio. The witess server must be ruig oe of the followig versios of SQL Server: SQL Server Express Editio, SQL Server 2008 or 2008 R2 Stadard Editio, SQL Server 2008 or 2008 R2 Workgroup Editio, or SQL Server 2008 or 2008 R2 Eterprise Editio. Database mirrorig is ot available with SQL Server Embedded Editio.

228 Chapter 8 SQL Server 2008 High Availability 211 Permissios. Your mirror database istace must provide the same permissios ad roles that are grated to your pricipal database istace. Recovery model. The database targeted for database mirrorig must be backed up usig the Full recovery model. The followig steps provide a example of how to eable ad cofigure SQL Server database mirrorig with a pricipal, mirror, ad witess server. 1. Ope SQL Server Maagemet Studio ad right-click o the target database for database mirrorig. Select the Properties item from the meu. 2. Whe the Database Properties dialog box opes (see Figure 8.1), click the Mirrorig page lik i the left pae. 3. This actio opes the Mirrorig page (see Figure 8.12) with most of its optios disabled. Click the Cofigure Security butto to cofigure the database mirrorig security settigs. Figure 8.12 The Mirrorig page of the Database Properties dialog box; most of its fields are disabled util database mirrorig has bee cofigured through the Cofigure Security butto.

229 212 SharePoit 2010 Disaster Recovery Guide Figure 8.13 The opeig scree of the Cofigure Database Mirrorig Security Wizard. 4. This opes the Cofigure Database Mirrorig Security Wizard, as show i Figure 8.13; click the Next butto to cotiue. 5. The wizard ext prompts you for witess server cofiguratio iformatio (see Figure 8.14). If you wat to set up a witess server ad eable automatic failover for this database mirrorig cofiguratio, select the Yes optio ad click the Next butto. If ot, select the No butto ad click the Next butto. I this example, select the Yes optio butto to cofigure a witess server. 6. The wizard s Choose Servers to Cofigure scree opes (see Figure 8.15), displayig the three database mirrorig server roles that ca have the database mirrorig security cofiguratio saved o them, with check boxes to the left of them. The check boxes for the pricipal ad mirror server istaces are checked by default ad disabled to prevet the selectio from beig modified. The witess server istace check box is checked by default but ca be uchecked. Esure that all three server istaces are checked, ad click the Next butto to cotiue. Note: If you choose ot to cofigure a witess server, the third server role is ot displayed i the scree.

230 Chapter 8 SQL Server 2008 High Availability 213 Figure 8.14 The Iclude Witess Server scree of the Cofigure Database Mirrorig Security Wizard. Figure 8.15 Wizard. The Choose Servers to Cofigure scree i the Cofigure Database Mirrorig Security

231 214 SharePoit 2010 Disaster Recovery Guide Figure 8.16 The Pricipal Server Istace scree i the Cofigure Database Mirrorig Security Wizard. 7. This opes the wizard s Pricipal Server Istace scree (see Figure 8.16). I this scree, you are show the curret database istace hostig the pricipal database for the mirrorig process i a disabled drop-dow meu. I this widow, you ca opt to have SQL Server ecrypt each trasactio as it is set from the pricipal server by selectig the associated check box, specify the etworkig port that the pricipal server uses to commuicate with the mirror ad witess server, ad reame the edpoit for trasactios set from the pricipal server. Whe you have etered the iformatio ad cofiguratio data for your pricipal database istace, click the Next butto to cotiue. Tip: If you have previously established a database mirrorig edpoit for the target database, the Ecrypt Data check box, the Listeer Port text field, ad the Edpoit Name text field are disabled, prevetig you from modifyig the cofigured edpoit. To chage the curret mirrorig edpoit, you must execute Trasact-SQL commads to DROP or ALTER the mirrorig edpoit. 8. The wizard proceeds to the Mirror Server Istace scree (see Figure 8.17), which looks similar to the Pricipal Server Istace scree i Figure 8.16, except that the database

232 Chapter 8 SQL Server 2008 High Availability 215 Figure 8.17 The Mirror Server Istace scree i the Cofigure Database Mirrorig Security Wizard. selectio drop-dow meu is ow eabled. I this scree, you ca select the database istace hostig the mirror database for the mirrorig process from the drop-dow meu. If the desired database istace is ot available i the drop-dow meu, click the Coect butto to ope a dialog box to log ito the database istace or select the Browse for More optio from the drop-dow meu. After selectig the curret database istace, you ca opt to have SQL Server ecrypt each trasactio as it is set from the mirror server by selectig the associated check box, specify the etworkig port that the pricipal server uses to commuicate with the mirror ad witess server, ad reame the edpoit for trasactios set from the pricipal server. If you attempt to select the same database istace as the oe you established as the pricipal server, SQL Server displays a error message istructig you to select aother istace, ad the Next butto is disabled (see Figure 8.18). After you have etered valid iformatio ad cofiguratio data for your mirror database istace, click the Next butto to cotiue. 9. The wizard agai opes a scree similar to the Pricipal Server Istace scree i Figure 8.16 the Witess Server Istace scree (see Figure 8.19) ad it has the database selectio drop-dow meu eabled. I this scree, you ca select the database istace hostig the witess database for the mirrorig process from the drop-dow meu. If the desired database istace is ot available i the drop-dow meu, click the

233 216 SharePoit 2010 Disaster Recovery Guide Figure 8.18 The Mirror Server Istace scree i the Cofigure Database Mirrorig Security Wizard displayig a error whe the pricipal database istace is also submitted as the mirror istace. Coect butto to ope a dialog box to log ito the database istace, or select the Browse for More optio from the drop-dow meu. After selectig the curret database istace, you ca opt to have SQL Server ecrypt each trasactio as it is set from the witess server by selectig the associated check box, specify the etworkig port that the pricipal server uses to commuicate with the mirror ad witess server, ad reame the edpoit for trasactios set from the pricipal server. Like the mirror server scree, if you attempt to select the same database istace as the oe you established as the pricipal or mirror server, SQL Server displays a error message similar to Figure 8.18 istructig you to select aother istace, ad the Next butto is disabled. After you have etered valid iformatio ad cofiguratio data for your witess database istace, click the Next butto to cotiue. Note: If you opt ot to iclude a witess server i step 5 or ot cofigure its security i step 6, this scree is ot displayed. 10. The Service Accouts scree opes, allowig you to specify a service accout i DOMAIN\ACCOUNT format for each of the servers i the database mirrorig cofiguratio. As Figure 8.20 shows, the scree provides istructios regardig whe

234 Chapter 8 SQL Server 2008 High Availability 217 Figure 8.19 The Witess Server Istace scree i the Cofigure Database Mirrorig Security Wizard. Figure 8.20 The Service Accouts scree i the Cofigure Database Mirrorig Security Wizard.

235 218 SharePoit 2010 Disaster Recovery Guide Figure 8.21 The Complete the Wizard scree i the Cofigure Database Mirrorig Security Wizard. accouts should ad should ot be specified, as well as what actios SQL Server takes if the accouts listed do ot curretly have SQL Server logis. Oce you ve cofigured the accout iformatio, click the Next butto to cotiue. Note: If you opt ot to iclude a witess server i step 5, the text field for the Witess Service accout is ot displayed. 11. The last scree of the wizard is ow displayed (see Figure 8.21), allowig you to review what you have cofigured before clickig the Fiish butto to fialize the security cofiguratio process. If you see ay items that eed to be modified, click the Back butto to avigate to them ad make your chages. Whe you are ready, click the Fiish butto to complete the wizard ad have SQL Server begi to cofigure the database moitorig cofiguratio s security. 12. The Cofigurig Edpoits scree (see Figure 8.22) displays the progress of the security cofiguratio as it executes. Oce the tool is fiished, esure that all tasks have completed with a status of Success, review the status messages ad reports as eeded, ad click the Close butto to retur to the Mirrorig page of the database s Properties widow.

236 Chapter 8 SQL Server 2008 High Availability 219 Figure 8.22 The Cofigurig Edpoits scree i the Cofigure Database Mirrorig Security Wizard. Figure 8.23 The Database Properties dialog box prompts the user to either start or ot start database mirrorig usig the provided cofiguratio. 13. After SQL Server has completed the edpoit cofiguratio process, the wizard closes ad you are prompted with a widow askig if you wat to start database mirrorig for the target database usig the cofiguratio that just completed, as show i Figure Click the Start Mirrorig butto if you are ready to eable the process, or click the Do

237 220 SharePoit 2010 Disaster Recovery Guide Figure 8.24 The Mirrorig page of the Database Properties dialog box after the Cofigure Database Mirrorig Security Wizard has completed without error. Not Start Mirrorig butto if you are ot. I this example, the Do Not Start Mirrorig butto was clicked. 14. Regardless of whether you choose to start the mirrorig process, whe you retur to the Mirrorig page, it is apparet that may more fields are ow eabled after security was cofigured, as show by Figure I the Server Network Address sectio, the text fields for the Pricipal, Mirror, ad Witess servers are ow eabled ad populated with the etwork coectio strig used to cotact each of these servers. If you did ot start mirrorig i step 13, oly the Start Mirrorig butto is eabled. If you did start mirrorig i step 13, the Pause, Remove Mirrorig, ad Failover buttos are eabled. I the Operatig Mode sectio, the High Performace (Asychroous) ad High Safety with Automatic Failover (Sychroous) optio buttos are eabled if you chose to iclude a witess server i step 5. If you did ot iclude a witess server i step 5, the

238 Chapter 8 SQL Server 2008 High Availability 221 High Performace (Asychroous) ad High Safety Without Automatic Failover (Sychroous) optio buttos are eabled. I both cases, the latter radio butto is selected by default. The Status sectio cotais a text box displayig the database mirrorig status for the database ad a Refresh butto, which is disabled if mirrorig has ot bee started. If the Status field idicates that the database has ot bee cofigured for mirrorig, click the Start Mirrorig butto to iitiate the process. 15. After mirrorig has bee started for the database, you ca susped the process by clickig the Pause butto. A dialog box is displayed askig you to cofirm your request, ad you are the retured to the Mirrorig page. The former Pause butto is ow marked as the Resume butto ad ca be clicked to resume the mirrorig process for the database. Note: Pausig the mirrorig process places the mirrored database i a suspeded status ad results i trasactios ot beig trasferred from the pricipal database to the mirrored database util mirrorig is resumed. You ca use the Pause optio as a short-term solutio to improve performace o the pricipal database istace, but you should ot use it for exteded periods. The trasactio log of the pricipal database is ot trucated while mirrorig is paused so that all logged trasactios ca be set to the mirrored database oce the process is resumed. If mirrorig is ot resumed i a timely fashio, the trasactio log ca grow too large ad use all of its available disk space, ultimately causig a outage of the pricipal database if it caot write to its trasactio logs. 16. To completely stop the database from beig mirrored, click the Remove Mirrorig butto. A dialog box is displayed askig you to cofirm your request, ad you are the retured to the Mirrorig page. To restart mirrorig for this database, you must maually re-create all the cofigured mirrorig settigs. This actio permaetly removes the mirrorig associatios ad security settigs betwee the pricipal, mirror, ad witess servers, but the copy of the mirrored database is ot deleted from the mirror database istace. Note: If you chose to keep the mirrored database, you must perform a Restore with Recovery actio agaist it to make it available, because it was origially created usig Restore with No Recovery. You should cosider reamig the mirrored database to avoid cofusio betwee it ad the pricipal database. 17. To maually fail a database over from its pricipal to its mirror, click the Failover butto. A dialog box is displayed askig you to cofirm your request, ad you are the retured to the Mirrorig page. After completig the failover, the mirrorig server roles of the two databases have bee swapped, so the origial pricipal ow has the mirror role ad the origial mirror is ow the pricipal database.

239 222 SharePoit 2010 Disaster Recovery Guide Note: Keep i mid that this chage of roles has oly occurred i SQL Server from a mirrorig perspective; it does ot commuicate this update to the applicatios or services that use the database ad may ifluece their ability to access the database. 18. If you wat to chage the operatig mode of the mirrorig process, simply select the butto ext to the optio you wat ad click OK, closig the database s Properties widow ad savig your chages. Step 14 briefly discussed a crucial compoet of SQL Server s database mirrorig fuctioality: the operatig mode. The optio you select for this sectio directly impacts how SQL Server hadles your mirrored database i the case of a outage. The three optios available are described ext: High Performace (Asychroous). This operatig mode commits chages to the pricipal database, seds them to the mirror, ad the proceeds with ormal processig without waitig for cofirmatio by the mirror server that the trasfer was successful. High Performace mode offers improved performace because the pricipal server is ot waitig o the mirror server to execute operatios, but there is also a icreased risk of error due to the lack of cofirmatio. This database mirrorig mode is better suited whe the operatioal performace of the database is more importat to your orgaizatio ad a zero-loss RPO is t a strict requiremet. High Safety Without Automatic Failover (Sychroous). This operatig mode does ot mark a trasactio as completed util it has bee writte to the trasactio log of both servers. Because it does ot require a witess server, the database must be maually failed over to the mirror i the case of a outage. If your orgaizatio requires that a mirrored database meet a zero-loss RPO target, High Safety Without Automatic Failover is the best database mirrorig choice available. High Safety with Automatic Failover (Sychroous). This operatig mode does ot mark a trasactio as completed util it has bee writte to the trasactio log of both servers, but it does provide automatic failover because it requires a witess server. High Safety with Automatic Failover mode is best suited if your orgaizatio places a high priority o realtime RTO targets for databases; the availability of automatic failover meas that the database s dowtime is limited to the time it takes to brig the mirror olie. As previously stated, oe of the most attractive features for database mirrorig is its ability to provide automatic failover capabilities for your SharePoit databases i the evet of a outage o your pricipal database istaces. It is also importat to uderstad that this importat feature is oly available with oe of database mirrorig s three operatioal modes: High Safety with Automatic Failover. Neither High Performace or High Safety Without Automatic

240 Chapter 8 SQL Server 2008 High Availability 223 Failover allows for the mirrorig cofiguratio to be redirected from the pricipal to the mirror should a error occur o the pricipal. This fact, combied with some compatibility issues discussed i the followig sectio, makes the operatig modes without automatic failover much less compellig ad useful. If you wat to create a secodary copy of a database without automatic failover, cosider usig log shippig or database backups before usig database mirrorig. Both log shippig ad backups require far less i terms of IT resources to implemet ad are much more flexible tha database mirrorig with the ability to create multiple redudat copies of a sigle database somethig ot possible with mirrorig. I geeral, take some time to carefully cosider the requiremets ad implicatios of your optios prior to implemetig database mirrorig i your eviromet. The choice you make directly affects your database architecture, the performace of your system, ad your disaster recovery ad HA plaig. SharePoit ad Database Mirrorig If you have had ay experiece usig database mirrorig as a HA solutio for previous versios of SharePoit, you kow that it was t a very good story. It was t as if the two solutios were icompatible, but there was a major piece of the puzzle that just was t there: true automatic failover. SQL Server s High Safety with Automatic Failover operatig mode worked just fie ad was defiitely capable of failig over from the pricipal to the mirror whe the situatio called for it, but the problem was that SharePoit had o way of kowig that a failover had happeed. Ad because it did t kow about failovers, it could t automatically update itself to poit at the mirror istead of the pricipal, which meat that every server i a give SharePoit farm would have to be updated every time a failover occurred to poit the farm at the correct database istace ad database ames. The good ews is that we have a much differet story to tell about database mirrorig with SharePoit It comes dow to this: SharePoit 2010 is ow mirrorig aware, which meas it ca recogize whe SQL Server automatically fails databases from the pricipal to the mirror ad update its cofiguratio throughout the farm accordigly. Huma itervetio or custom scriptig is o loger required to set up SharePoit to properly use database mirrorig as a SQL Server HA solutio. SharePoit Database Mirrorig Recommedatios ad Requiremets Microsoft has stated several recommedatios ad requiremets you should uderstad, follow, or make your best effort to follow to achieve the best possible stability ad cosistecy for your SharePoit database mirrorig cofiguratio. The followig list outlies several of these items ad describes their purpose: Network latecy less tha oe millisecod. Latecy is the time it takes for a data packet to travel from oe poit to aother over a etwork. It ca be measured for oe-way trips or for roud trips, although the latter is used much more commoly. The less latecy your etwork has, the faster data moves betwee your servers. Database mirrorig requires low latecy to esure that the mirror is kept as closely sychroized with the pricipal as possible. Oe

241 224 SharePoit 2010 Disaster Recovery Guide major cause of etwork latecy is physical distace, which meas that pricipal ad mirror servers ofte eed to be located ear each other ad elimiates some of the true redudacy of the solutio. Please ote that this is a recommeded value, ot a requiremet. Network badwidth oe gigabyte per secod (GB/s) or greater. Badwidth measures the amout of data that ca be trasferred over a etwork withi a give period of time, usually oe secod. Microsoft recommeds (ot requires) that your etwork be capable of trasferrig at least 1GB of data per secod betwee odes i the etwork, due to the high amout of data that will be i the target databases trasactio logs as they are copied from the pricipal to the mirror. Physical computig resources. Microsoft recommeds that both the physical ad mirror SQL Server hosts be provisioed with sufficiet processig, memory, storage, ad etworkig resources to accomplish mirrorig without impact o performace. Note the umber of databases you are goig to mirror i your eviromet; the more databases you mirror, the greater the strai o your servers. The good ews is that, by default, database trasactio logs are compressed by SQL Server 2008 as they are set from the pricipal to the mirror. That does require more processig power to compress the files, but it esures that the smallest possible file is set over the etwork, which reduces etwork traffic ad shortes the time it takes to deliver each file. Database recovery model. As oted earlier i this chapter, database mirrorig requires that the target database is backed up usig the Full recovery model. By default, SharePoit creates several databases that are cofigured to use the Simple recovery model; you are required to chage that settig to cofigure them for mirrorig ad eed to accout for the additioal overhead that accompaies chage. Database permissios. The service accouts used by various compoets i your SharePoit eviromet must be cofigured to have the same rights i the SQL Server istace hostig the mirrored database as they do i the pricipal SQL Server istace. Pay attetio to the rights grated the service accout servig as the idetity of all SharePoit s IIS applicatio pools (especially the accout for the Cetral Admiistratio site), the database access service accout, the default cotet access accout, all accouts associated with Service Applicatios, ad user accouts that have bee added to the Farm Admiistratios SharePoit group. Uique istace ames. If possible, do ot cofigure the SQL Server istace hostig mirrored databases with the same server ad istace ames as the pricipal istace. This ca add a great deal of uecessary cofusio ad complexity to your eviromet ad make it difficult to determie which istace is curretly hostig which role i the cofiguratio. SQL aliases. You ca use SQL Server aliases to abstract the actual address of a SQL Server istace, allowig a cliet computer to be cofigured to target the alias rather tha the SQL

242 Chapter 8 SQL Server 2008 High Availability 225 Server istace directly. This abstractio is helpful for applicatios that have strog ties to their databases, such as SharePoit, because it adds more flexibility o the use of those database resources tha is ormally available. If the address for that SQL Server istace should chage, or if a differet server altogether is used, all that is required is a chage to the SQL Server alias, rather tha a major cofiguratio chage to the applicatio. SQL Server aliases make database itegratio ad maagemet much easier for SharePoit i geeral ad should be used wheever possible i your mirrorig cofiguratio. Should a mirrorig target chage, oce the chage is made i SQL Server s setup, you ca update SharePoit via a small modificatio to the alias istead of a complex chage to the farm s cofiguratio. Operatioal mode. SharePoit ca oly be cofigured for awareess of database mirrorig cofiguratios that are usig the High Safety with Automatic Failover operatioal mode. If either of the other two operatioal modes are used to cofigure the mirror ad SQL Server fails over from the pricipal database to its mirror, admiistrator itervetio or custom scriptig is required to poit SharePoit at the mirror database istead of the pricipal. How to Cofigure SharePoit for Database Mirrorig The first thig you eed to do if you wat to set up database mirrorig for your SharePoit farm s databases is to actually cofigure the mirrorig i SQL Server, usig the iformatio ad steps outlied earlier i this chapter. Make sure to take ito accout the items listed i the SharePoit Database Mirrorig Recommedatios ad Requiremets sectio, because they are crucial toward esurig the best possible stability ad itegratio for your mirrorig cofiguratio i cojuctio with your SharePoit eviromet. Oce mirrorig is cofigured i SQL Server, you have two optios available for makig your SharePoit farm aware of your mirrored databases: the SharePoit Cetral Admiistratio Site ad PowerShell. Tip: Please ote that you are resposible for settig up the mirrorig cofiguratio i SQL Server for the databases that you wat to mirror; SharePoit 2010 does ot do that cofiguratio for you. But the good ews is that it does validate the mirrorig cofiguratio to esure that it is properly set up ad eabled oce you otify SharePoit that a give database is mirrored. If you are most comfortable admiisterig SharePoit through its graphical user iterface (GUI), the Cetral Admiistratio site, you should be glad to hear that you ca register SharePoit s cotet databases as mirrored i it. But, ad this is a pretty big but, keep i mid that we said cotet databases there. You ca oly use the Cetral Admi site to register mirrorig for SharePoit cotet databases associated with a Web applicatio, ot Service Applicatio databases or the farm s cofiguratio database. These items ca still be made mirrorig aware withi SharePoit; it s just that you must use PowerShell to do so.

243 226 SharePoit 2010 Disaster Recovery Guide Figure 8.25 The Maage Cotet Databases page i the SharePoit Cetral Admiistratio site. Because of this limitatio, registerig a cotet database as mirrored i the Cetral Admi site is best used for oe-off situatios rather tha a wholesale activity for every database withi the farm. To set up a cotet database to make it aware of its mirrorig cofiguratio, see the istructios that follow: 1. Ope the Maage Cotet Databases page. (It s foud i the Databases sectio of the Applicatio Maagemet page.) See Figure 8.25 for a example of the Maage Cotet Databases page i the Cetral Admiistratio site. 2. I the Maage Cotet Databases page, click the lik for the cotet database you have mirrored i SQL Server to ope the Maage Cotet Database Settigs page (see Figure 8.26). 3. Oce the Maage Cotet Databases page opes, locate the Failover Server sectio (circled i Figure 8.26). Eter the fully qualified domai ame (FQDN) of the server (or the SQL alias poitig to it that you cofigured o the SharePoit server, which we highly recommed) hostig the mirror versio of the database i the Failover Database Server field, ad click the OK butto at the bottom of the page to save your chages. If SharePoit is able to validate the mirrorig cofiguratio, you are retured to the Maage Cotet Databases page without error. If you prefer doig your admiistratio from the commad lie, or you wat to cofigure mirrorig awareess for SharePoit databases other tha cotet databases, PowerShell is the way

244 Chapter 8 SQL Server 2008 High Availability 227 Figure 8.26 site. The Maage Cotet Databases Settigs page i the SharePoit Cetral Admiistratio to go. Use the Get-SPDatabase cmdlet to obtai a object based o the ame of the SharePoit database you are mirrorig, ad the update that object s AddFailoverServiceIstace property with the ame of the SQL Server istace hostig the mirrored database. For more iformatio o PowerShell ad its vastly expaded role i SharePoit admiistratio, see Chapter 10. Although you have to make some tough decisios whe cofigurig database mirrorig for use with SharePoit s databases, a good portio of your cofiguratio choices is drive by other factors maily, how your ifrastructure is or ca be implemeted to meet your eeds. For some eterprises, it may ot be cost effective to implemet multiple farms i geographically diverse locatios, whereas for others it may be a busiess-critical requiremet, ad each optio (plus all those i betwee) affects how you ca use database mirrorig ad what ca be mirrored. For a sigle farm eviromet with compoets hosted i multiple dataceters, agai you ca use all three operatig modes, but i this case you eed to address stickig poits as part of the architecture. I this type of eviromet, the mirrored database istace is hosted i a separate dataceter from the pricipal istace, providig geographical redudacy i the case of a outage. If you are usig multiple dataceters to host your database mirrorig cofiguratio, pay special attetio to the latecy ad badwidth requiremets listed previously i this sectio.

245 228 SharePoit 2010 Disaster Recovery Guide These costraits mea that the dataceters must be capable of providig large, fast coectios to the servers they host ad that, i most cases, these dataceters must be located closely to reduce latecy (at the cost of icreasig risk to localized catastrophes). Additioal Witess Server Cosideratios If a witess server is cofigured for automatic failover, Microsoft recommeds placig it i a third dataceter to esure that it ca iitiate the failover process i case of a outage o the pricipal server. Because this may ot always be a feasible cofiguratio, it is still possible to host the witess server i oe of the two dataceters, but you must uderstad that it is exposed to the same risks as the other servers hosted with it, ad a maual failover is required if the witess server is impacted by a outage. Microsoft also recommeds hostig the witess server i the same dataceter as the mirrored istace so that a potetial outage o the pricipal has a reduced chace of affectig the witess server as well, but this is ot without its ow drawbacks. Whe the witess is i the same dataceter as the mirror, a loss of the coectio betwee it ad your pricipal istace s dataceter ca brig your etire database eviromet dow. This is because of the way that database mirrorig s quorum requiremets work: if the pricipal caot cotact the witess or the mirror to establish a quorum, it also shuts dow because it caot maitai trasactioal stability. Regardless of where you place it withi your eviromet, we strogly recommed icludig the witess server i ay moitorig solutios you may establish, ot oly to track the status of the mirrorig process but to cofirm that the witess server is healthy ad able to execute the failover whe eeded. If you have multiple farms i separate dataceters, the sychroous operatig modes for database mirrorig really are ot a optio because of the time it would take for a trasactio to be set across the etwork ad writte to each database, ad the results set back across the etwork. These activities are directly iflueced by etwork latecy somethig that is uavoidable over a wide area etwork (WAN) coectio betwee dataceters that do ot share large, fast coectios. You ca still use database mirrorig with the asychroous operatig modes to provide mirrored copies of your crucial SharePoit data. The other drawback to usig mirrorig for multiple farms is that, like log shippig, you ca use it oly to mirror your cotet databases or Service Applicatio databases as log as their associated Service Applicatio is ot hostig SharePoit s search fuctioality. Tip: If usig the High Performace (Asychroous) or High Safety Without Automatic Failover operatig modes for your mirrorig cofiguratio, there is o beefit to havig a witess server. Witess servers are oly required to provide automatic failover capabilities for a mirrorig cofiguratio usig the High Safety with Automatic Failover operatig mode; they are uecessary whe usig the other two operatig modes.

246 Chapter 8 SQL Server 2008 High Availability 229 Database Mirrorig Pros Are you still usure whether database mirrorig is the best HA solutio for your SQL Server 2008 istaces ad SharePoit databases? The followig list describes the strog poits of database mirrorig ad their beefits for SharePoit to help you with your decisio: Idepedet. Like log shippig, database mirrorig s fuctioality is ot tied to SharePoit, or is it affected by ay other processes i the SQL Server database istace. This meas that chages to your SharePoit cofiguratio or its databases do ot directly impact or harm your database mirrorig procedures. Highly cofigurable. There are several optios ad cofiguratios to be set to allow database mirrorig to meet the eeds of your eviromet. Easily cofigurable. Not oly is database mirrorig straightforward for a admiistrator to set up ad cofigure, but the ifrastructure to host it does ot require specific hardware to implemet it. Keep i mid that this does ot ecessarily mea it is easy to operate. Immediate. Whe a chage is made to a pricipal database, it is also immediately set to the mirror. Automated. If a witess server is cofigured alog with the pricipal ad mirror servers, whe a outage occurs, a failover from the pricipal to the mirror ca be automatically executed without admiistrator itervetio, especially whe combied with SharePoit 2010 s awareess of mirrorig cofiguratios. Resposive. Failovers are executed quickly, regardless of whether they are maually or automatically requested. Distributed ad redudat. As previously explaied, you ca use database mirrorig i various ways to esure the log-term stability of your SQL Server eviromet ad the SharePoit farm that depeds o it. Database Mirrorig Cos Database mirrorig also comes with its ow set of drawbacks that you must cosider before decidig to implemet it, as described here: Oe mirror per database. A database caot be mirrored more tha oce, creatig a sigle poit of failure for your HA solutio. Regularly test ad cofirm your database mirrorig cofiguratio to esure that it cotiues to fuctio as expected. No easy read-oly optio. Mirrored databases caot be made available for read-oly queryig without the creatio of a additioal sapshot based o the mirror. Operatioal mode limitatios. Although you ca use SharePoit with all three operatioal modes for SQL Server database mirrorig, the oly mode that it makes sese to use is High

247 230 SharePoit 2010 Disaster Recovery Guide Safety with Automatic Failover. SharePoit is ot capable of automatically failig over to a mirrored database with the High Performace or High Safety Without Automatic Failover modes, ad some SharePoit databases ca oly be mirrored with the High Safety with Automatic Failover mode or ot at all. (See cc aspx for more iformatio o SharePoit Server 2010, its databases, ad what ca or caot be mirrored.) Because the other operatioal modes do ot offer the valuable feature of automatic failover, if you are ot able to use the High Safety with Automatic Failover mode, or you do ot wat to use it, you may fid that you are better served usig log shippig to protect your SharePoit databases, rather tha mirrorig. Performace impact. Database mirrorig requires multiple processig threads o its host servers, which ca egatively affect the performace of your databases i geeral (specifically utilizig CPU ad RAM), especially as more ad more databases i the istace are mirrored. If you pla to highly utilize database mirrorig, make sure you have the horsepower to accout for it. Depedece o etworkig. Attemptig to do sychroous database mirrorig i a etwork with suboptimal badwidth or latecy leads to performace issues for your pricipal database ad the SharePoit eviromet that uses it. Geographical limitatio. Although database mirrorig ca be distributed across multiple dataceters, Microsoft has stated that these dataceters caot be more tha a few miles away from each other, which limits its ability to deliver true geographical redudacy. Iability to cofigure failover criteria. Admiistrators caot cofigure or maage the criteria that SQL Server uses to determie whe the cofiguratio should be failed over from the pricipal to the mirror. Because SharePoit 2010 is ow mirrorig aware, this is less of a cocer, but it is still problematic that you caot cofigure its toleraces to allow for the specific state of your eviromet. Icompatibility with RBS. Databases cofigured to use RBS caot be mirrored, regardless of whether they are usig Microsoft s FILESTREAM provider or a third-party provider. Complexity. Database mirrorig ca be a order of magitude more ivolved to implemet tha SQL Server backups or log shippig. It takes careful research ad plaig to develop a mirrorig solutio that is completely compatible with your ifrastructure, SQL Server, ad SharePoit cofiguratios, due to mirrorig s specific requiremets. These requiremets ad several of the items listed ca also make operatio of a mirrored eviromet challegig. Database mirrorig is certaily a viable HA solutio for SQL Server that s worth serious cosideratio. It lets you automatically fail over to a fallback database istace should your productio database fail. It also gives you the cofidece of kowig that the data i your fallback istace is a exact copy of your productio database. It is flexible ad ca be used with various hardware ad software cofiguratios. But you may fid that it is ot a good fit for the eeds of

248 Chapter 8 SQL Server 2008 High Availability 231 a orgaizatio ad its HA requiremets. What if you eed your databases to always be olie ad caot suffer a outage of eve a hour while you update your SharePoit farm to poit at your mirrored database istace? What if you eed more tha oe fallback istace to add additioal redudacy to your eviromet but the performace implicatios of log shippig rule it out as a optio? These are just two examples of whe cofigurig a cluster of servers ruig SQL Server may be the best solutio to your problems. Database Clusterig Clusterig is ot uique to SQL Server or eve to database platforms i geeral. A server cluster cosists of two or more servers, each cofigured idetically, that are desiged to cosistetly serve up a applicatio or platform eve if a error or outage occurs o oe of the members of the cluster. Although this sectio focuses o how to use clusterig with SQL Server, you ca use it to provide HA capabilities for various platforms, such as Microsoft Exchage, Microsoft Hyper-V, ad may more. This sectio puts the spotlight o the failover clusterig solutio icluded i Widows Server 2008, but it is by o meas the oly clusterig platform available to you for your SharePoit ad SQL Server eviromet. Other clusterig solutios are available i the marketplace to provide a viable HA solutio for your database eviromet, each offerig uique fuctioality, optios, ad challeges to give you some flexibility over how you cluster your SharePoit database. Although some products may be specific to the UNIX or Liux platforms, others, such as Symatec s Veritas Cluster Server, are completely compatible with SharePoit ad SQL Server ad have bee successfully implemeted as eterprise clusterig solutios i the most demadig of situatios. Note: The decisio to highlight Widows Server failover clusterig i this sectio is ot meat to edorse it as a clusterig product or idict its competitors. The goal is to show you how to implemet a widely used clusterig product for your SharePoit ad SQL Server eviromet, ot laud oe product over aother. It is up to you to evaluate the products i this space ad determie which oe is the best solutio for your eterprise, its ifrastructure, ad its requiremets. Like so may other aspects of SharePoit, this is ot a oe-size-fits-all kid of situatio. The Server Compoets of Widows Server Failover Clusterig Oe advatage of clusterig as the HA solutio for your SQL Server eviromet is the flexibility it gives you i desigig the architecture of your solutio. To create a cluster, you eed at least two servers; that way you ca create two separate odes withi the cluster. Clusterig s flexibility is that you ca place more tha oe server i a ode (failover clusterig allows up to 16 servers i a ode, depedig o the editio of Widows Server 2008 beig used), ad you are

249 232 SharePoit 2010 Disaster Recovery Guide ot required to have the same umber of servers i each ode. So if you wat to create a ode with oe server ad a ode with two servers, that optio is available to you. You ca also have up to 16 odes i a cluster. Each ode is expected to be able to serve as the primary provider of database services for the cluster, so that if a ode is take dow or suffers a outage, you ca brig aother ode i the cluster olie to cotiue that service with o or little dowtime. Failover clusterig is available as a icluded compoet of Widows Server 2008 s Eterprise ad Dataceter editios. Microsoft is careful to state that failover clusterig is iteded to be used as a HA solutio but is ot completely fault tolerat. Fault tolerat describes systems ad solutios desiged with a extremely high degree of redudacy ad the ability to provide early istataeous recovery times; the dowside is that these systems ofte come with a prohibitively high price tag to match. Failover clusterig was desiged to eable systems to be highly available while usig stadardized, cost-effective hardware ad software, rather tha the specialized systems leveraged by a fault-tolerat solutio. This is ot to say that failover clusterig is ecessarily a low-cost solutio, but it ca implemet a effective HA solutio failover clusterig at a much lower cost tha a fully tricked-out solutio desiged to be fault tolerat. Some aspects of clusterig with failover clusterig are iflexible specifically the hardware required for the servers i the cluster ad the way that hardware must be cofigured. The followig list outlies the hardware ad etworkig eeds you are likely to ecouter for failover clusterig: Servers. As metioed previously, at least two servers must be available to create a database cluster with failover clusterig. Ulike log shippig ad database mirrorig, these servers caot host databases that exist outside the cluster. Take special care to evaluate the eeds of your database eviromet ad cofirm that the hardware cofiguratio you select ca meet those eeds i a clustered cofiguratio. Note: I Widows Server 2003, Microsoft Clusterig Services (MSCS) required the hardware used for a failover cluster to be o the Widows Hardware Compatibility List (HCL); that s chaged i Widows Server Now, a failover cluster s hardware must be marked by its vedor as Certified for Widows Server 2008, ad the etire cofiguratio must be validated with a ew tool, the Validate a Cofiguratio Wizard. (It is also kow as the Cluster Validatio Tool, or CVT.) This tool cosists of a series of simulatios ad tests desiged to cofirm that the hardware plaed for use i a failover cluster meets the specificatios ecessary to ru it. The Validate a Cofiguratio Wizard ca also be ru agaist a cofigured failover cluster as a additioal test of its cofiguratio to further esure that it is ready for use, somethig we strogly ecourage. Idetical cofiguratios. Each server withi the cluster must have a idetical cofiguratio for its RAM, CPU, system disk, ad so o.

250 Chapter 8 SQL Server 2008 High Availability 233 Redudat etwork hardware. Each server withi the cluster must have at least two etwork iterface cards (NICs): oe for commuicatio with the cliets accessig the database server, ad oe to coect to its cluster ode for heartbeat ad status updates. Advaced etwork hardware. Each server withi the cluster must be able to establish fast ad reliable commuicatios with the other members of the cluster, usually via specific hardware solutios such as a crossover cable (i the simplest case) or fiber optic cable. Specialized storage. Each server withi the cluster must be able to access a cetralized storage system, such as a storage area etwork (SAN), to access the data created, stored, ad updated by a cluster, such as database files. Failover clusterig follows the shared-othig model i its use of storage withi a cluster, meaig that all the servers i a cluster ca access the cluster s storage repository, but it is updated ad maaged by oly oe server at a time: the primary server or ode i the cluster. Note: The maximum amout of shared storage space that a SQL Server database ca use whe hosted i a failover cluster is 2 terabytes (TB). High-speed coectio to shared storage. Each server must have a high-speed coectio to the cluster s cetral storage, such as Small Computer System Iterface (SCSI), Fibre Chael (FC), or Iteret SCSI (iscsi). Network resources. At a miimum, you must provide a Network Basic Iput/Output System (NetBIOS) ame ad a uique static Iteret Protocol (IP) address for the cluster, as well as static IP addresses for all the NICs that servers withi the cluster use. Note: For more detailed iformatio from Microsoft o the hardware requiremets of Widows Server 2008 failover clusterig, see library/dd197454%28ws.10%29.aspx. Cofigurig Widows Server Failover Clusterig After you have procured, istalled, ad cofigured your hardware ad etwork solutio, you are ready to start cofigurig a database failover cluster usig SQL Server 2008 ad failover clusterig. Whe you have built your servers ad istalled the Widows Server 2008 operatig system o them, you must complete some prerequisite steps i the operatig system of each server: Eable the failover clusterig feature. You ca eable this feature from the Iitial Cofiguratio Tasks widow or the Server Maager i Widows Server 2008 Eterprise or Dataceter, as well as Widows Server 2008 R2 Eterprise or Dataceter.

251 234 SharePoit 2010 Disaster Recovery Guide Do ot istall ativirus. Microsoft recommeds ot istallig ativirus software o the server odes i your cluster, because it ca cause coflicts or problems with MSCS. Do ot compress hard drives. You must ucompress the hard drive o each server ode where SQL Server is to be istalled. Mout shared storage. Widows Server allows additioal drives or storage volumes to be mouted, icludig those preseted via shared storage. It also requires a drive letter to be assiged to each drive whe it is mouted, which limits a server to 25 mout poits. You ca avoid this latter limitatio by moutig a local physical drive to a letter, such as D, ad the moutig your shared volumes as directories uder the D volume, a process kow as a mout-poit folder path. Your system should ow be ready for failover clusterig to be cofigured ad a cluster to be created with at least two servers fuctioig as odes withi the cluster. Ufortuately, this chapter caot provide a walkthrough of how to cofigure a failover cluster; the shared storage required by the cluster is ot a resource that you ca easily acquire, ad the available techical resources for creatig the scearios ad walkthroughs i this book do ot iclude shared storage. The followig list highlights several issues to cosider as part of plaig ad cofigurig your server cluster with failover clusterig for it to host a SQL Server database istace: Cluster service accout. Microsoft recommeds the creatio of a service accout to be used as the idetity of the failover clusterig service ruig o each server ode i the cluster. This accout must be a domai accout grated Local Admiistrator rights o every server i the cluster. This accout must also be able to log ito your clustered SQL Server database istace with public rights to moitor its status. By default, the server s Local Admiistrators group has this right, but i some cases database admiistrators remove that access as a security measure. SQL Server service accouts. The service accouts to be used as the idetity of SQL Server s various services ruig o each server ode i the cluster must be domai accouts, ot local accouts o each server ode. Turig o ad off server odes ad storage. Review Microsoft s istructios for cofigurig failover clusterig ( 29.aspx), because they cotai specific iformatio regardig whe to tur o ad off the various server odes ad storage resources durig a cluster s cofiguratio. Quorum mode. With Widows Server 2008, Microsoft chaged the way failover clusterig tracked the status ad health of the cluster. MSCS previously used a storage resource, called a quorum disk, to store the cluster s cofiguratio data ad log files o a dedicated volume, which was ievitably a sigle poit of failure. Failover clusterig s ew approach for determiig quorum requires that each ode submit a vote for its status, ad if a majority

252 Chapter 8 SQL Server 2008 High Availability 235 of votes are available, the cluster has achieved quorum. This removes the depedecy o a sigle item, makig failover clusters much more stable. You ca actually use multiple quorum modes i a failover cluster; the Validate a Cofiguratio Wizard recommeds a quorum mode whe it rus, ad Microsoft s advice is to use that recommedatio uless you have specific reasos to select aother mode. Failover Cluster Maagemet applicatio. If your istalled versio of Widows Server 2008 icludes the failover clusterig feature, you ca fid this applicatio i the Start meu s Admiistrative Tools directory. This is the tool you must use to create ad maage your server clusters. Cluster ame. The ame of your cluster should follow Domai Name Services (DNS) amig rules. You ca use upper- ad lowercase letters, umbers, ad dashes i the ame, which must be betwee 1 ad 63 characters. The ame should also be uique withi its paret domai. Storage cofiguratio optios. Whe ruig the New Server Cluster Wizard through the Cluster Admiistrator tool, i its Select Computer page, you are prompted to eter the ame of the first computer to be added as a ode i the ew cluster. This page also icludes a Advaced butto that, whe clicked, opes a dialog box where you ca allow the wizard to automatically cofigure the cluster s shared storage (called the Typical cofiguratio) or to maually do it yourself (Advaced cofiguratio). With the Typical cofiguratio, the wizard selects all the disks i the mouted shared source as disks available to the cluster ad creates resources withi the cluster for these disks. If you select the Advaced cofiguratio, you must use the Cluster.exe executable to cofigure the cluster s shared storage. Heartbeat. After you ve created the cluster ad added additioal server odes to it, make sure to cofigure the heartbeats that the cluster uses to cofirm that the etwork iterfaces for each ode are fuctioig properly. Without this cofiguratio, the cluster has o way to kow if a server ode is available withi a cluster. Cofiguratio review ad testig. Just because you have successfully created ad cofigured your cluster does ot mea your work is doe. You should immediately test your cluster ad cofirm that it fuctios without error ad is able to successfully fail over from oe ode to aother whe the primary ode is uavailable. Review all server logs to cofirm that o errors are beig reported withi the cluster. You should establish regular tests of this process, ad ay other cluster fuctios that you fid missio critical, to verify that the cluster cotiues to fuctio as desiged. Now that you have created your failover cluster, complete with at least two server odes withi it, you are ready to istall SQL Server ad create your database istace i the failover cluster. As with the creatio of the server cluster, due to resource limitatios, it s ot possible to provide you with a detailed descriptio of the steps ecessary to create your database istace

253 236 SharePoit 2010 Disaster Recovery Guide successfully. However, the followig is a checklist of items that you should review ad evaluate while completig the process: Follow SQL Server security best practices. Cofigure your ew istace with the same security settigs ad measures as oclustered istaces, while takig ito accout the special requiremets of the cluster service accout ad the fact that your SQL Server service accouts must be domai accouts. Istall SQL Server o a cluster. To istall SQL Server o each server ode i the cluster, simply log o to the cluster at its shared IP address (rather tha the address of the server actig as the active ode i the cluster) ad ru the SQL Server istaller. SQL Server is built to be aware of ad work i a clustered eviromet. The istaller ca detect the cluster eviromet ad istall the software to each server ode i the cluster you select through the wizard. Validate the compoets to istall. If you are istallig SQL Server via the GUI wizard, check the Create a SQL Server Failover Cluster check box i the Compoets to Istall page. It appears as a ideted item udereath the SQL Server Database Services check box ad is ot checked by default. You must check it for the istaller to istall SQL Server to all the odes withi the cluster. Determie how to ame your istaces. You ca create failover clusters usig either the default istace for the cluster or a amed istace. The choice is up to you. Review your failover cofiguratio. Istallig a sigle database istace i the cluster is referred to as a Active/Passive failover cofiguratio. You ca also cofigure multiple istaces to be hosted withi a sigle cluster, referred to as a Active/Active failover cofiguratio. I a Active/Active cofiguratio, you must assig each istace a differet primary server withi the cluster. This cofiguratio allows SharePoit s databases to be separated betwee the istaces for scalability purposes. Cautio: If you are cosiderig implemetig a Active/Active failover cofiguratio, remember that i a failover sceario, multiple active clusters ca be hosted o a sigle ode withi the cluster. This meas that each ode i the cluster must be cofigured with sufficiet hardware resources to host both clusters, or you must be willig to accept degraded performace for both clusters util a additioal ode ca be brought olie to accept oe of the active clusters. Correctly ame the virtual server. The value provided i the Virtual Server Name page of the istallatio wizard should be the ame of the cluster, ot the ame of the curret active ode withi the cluster. Istall SQL Server o every ode i the cluster. I the Cluster Node Cofiguratio page, select every server ode i the cluster so that SQL Server is istalled to all of them.

254 Chapter 8 SQL Server 2008 High Availability 237 Test your system. Whe the istallatio wizard completes, completely test your system to cofirm that the database istace is available to cliet coectios, is ot reportig errors, ad ca be successfully failed over from oe ode to aother. Establish regular tests of this process, ad ay other cluster fuctios that you fid missio critical, to verify that the cluster cotiues to fuctio as desiged. SharePoit ad Database Clusterig Now that you have successfully created a failover cluster for a SQL Server database istace, you ca cosider the implicatios of usig that istace to host SharePoit databases. Oe major advatage to the use of a failover cluster for your SharePoit database istace(s) is that you ca use it to host all types of SharePoit databases without a special cofiguratio (beyod what it takes to create ad cofigure the cluster). The oly step requirig specific attetio is how you idetify the address of the database istace whe creatig the SharePoit farm; you must submit the ame of the cluster, ot the ame of the active server ode for the cluster. Note: SharePoit 2010 requires that SQL Server 2008 be patched at least to Service Pack 1 (SP1) ad Cumulative Update 2 (CU2) if usig it i a failover cluster. SharePoit views the clustered istace as it does ay other database istace. Durig istallatio of your farm, it creates all its eeded databases without error. The cofiguratio, Cetral Admiistratio cotet, ad Search databases ca be hosted i the clustered istace because the ame of the cluster is used ad writte to these databases istead of the ame of the active server ode i the cluster. So, i the case of a outage o the active server ode, whe the cluster fails over to aother server ode, you ca still use these databases. The oly outage that SharePoit experieces is durig the failover itself; whe the ew active ode comes olie i the cluster, service is retured to ormal without requirig updates to the SharePoit farm. Note: Keep i mid that you ca use SQL aliases with a failover cluster, eve though the address for the clustered istace that SharePoit uses does ot chage regardless of which ode i the cluster is active. You should still cosider usig SQL aliases to further abstract the locatio of the clustered istace away from SharePoit to give yourself greater flexibility ad scalability with your SQL Server back ed. Database Clusterig Pros Database clusterig is a powerful, high-availability tool for SQL Server 2008 that offers several reasos for beig a viable optio for your SharePoit databases. The followig list covers the most compellig reasos for its use: True automatic failover. Whe a active ode withi a cluster suffers a outage or failure, the cluster automatically fails over to aother ode withi the cluster. Because SharePoit

255 238 SharePoit 2010 Disaster Recovery Guide refereces the idetity of the cluster ad ot a specific ode withi it, you do ot eed to update a farm s cofiguratio data to recogize the chage i database hosts. Patchig without outages. You ca complete Widows ad SQL Server patchig without makig the cluster itself uavailable. Simply apply your patches to the iactive odes i the cluster, the fail over the cluster maually to those update odes, ad patch the remaiig odes. You ca do this without iterruptig the services that the cluster provides by takig advatage of the cluster s failover fuctioality. Rapid failover. Clusterig your database meas that, i the case of a outage, your system has a drastically shorter time to retur to ormal service. It oly takes the amout of time required for the cluster admiistratio process to switch over to aother server i the ode; o maual itervetio or cofiguratio is required to implemet the failover. Scalable. Because Widows Server 2008, failover clusterig, ad SQL Server 2008 support up to 16 server odes withi a cluster ad use flexible shared techology for storage, you ca cofigure your clusterig solutio i a variety of ways to meet the eeds of your system ad easily expad it to grow with your system. Compatible with log shippig. Like database mirrorig, databases hosted with a cluster ca be log shippig to aother istace to provide eve more redudacy for your data. Note: Failover clusterig is also compatible with database mirrorig, but we would t recommed it because of the complexity ad high costs of implemetig such a hybrid solutio. Choice of SQL Server backup model. Ulike i database mirrorig, you ca back up databases i a cluster usig ay backup model. The oly exceptio to this is if you are also usig log shippig or database mirrorig with your cluster, i which case the costraits of the associated techology also apply. Database Clusterig Cos Ufortuately, database clusterig also comes with some disadvatages that ca prove to be stumblig blocks to its implemetatio. Followig are those disadvatages: Network requiremets. Although server odes withi a cluster ca be located i separate dataceters, the badwidth requiremets for heartbeats ad shared storage coectivity mea that odes usually caot be more tha a few miles from oe aother. SAN storage requiremets. The techology required to implemet shared storage, from both a hardware ad software perspective, requires special expertise to implemet, operate, ad maitai. This also adds a depedecy o yet aother system for your SharePoit eviromet s overall health ad well-beig.

256 Chapter 8 SQL Server 2008 High Availability 239 Costs. I additio to the effort required to implemet shared storage, the hardware ad software for the techology come at a high price. Various providers ad cofiguratios are available i the marketplace, but eve the low ed of the cost spectrum may prove prohibitive for your budget. Fault tolerace. Log shippig ad database mirrorig provide a certai level of fault tolerace because the redudat data they preserve is stored o a storage medium completely separate from that of its source. Because clusterig uses shared storage to store the data files for your databases, a outage to that shared storage cofiguratio affects your etire cluster ad the applicatios that use it. Coclusio At least oe blaket statemet ca be made whe it comes to SQL Server ad HA: o oe ever wats a database to crash or become uavailable, especially ot a SharePoit database. Ufortuately, eve with the improvemets that have bee made i the quality, speed, ad capacity of moder IT ifrastructure ad the software that rus o it, such evets are ievitable. Hard drives fail, etwork coectios are yaked, ad lightig strikes, o matter what you do to try to prevet it. Your resposibility as a admiistrator is ot to prevet the impossible; it is to desig your system so that whe disaster strikes, it has miimum impact o the least umber of users possible. Microsoft recogizes this, ad the solutios available to eable HA for SQL Server 2008 show the effort the compay has put ito helpig you succeed i your role. As a SharePoit admiistrator, you must be eve more cogizat of your system s depedecy o its database provider. A outage of your compay s itraet, for eve a hour, ca result i a drastic loss of productivity ad reveue. As SharePoit evolves as a applicatio platform, orgaizatios are fidig more ad more creative uses ad ways to stretch it to its limits. You eed your eviromet ad its back-ed databases to be as stable as possible, ad SQL Server HA plays a large role i creatig that stability. Log shippig, database mirrorig, ad clusterig offer attractive HA solutios for your database istaces, but they also come with drawbacks that you eed to carefully weigh ad test. It is somewhat frustratig that there is o cut-ad-dried solutio to specific HA circumstaces, but this is ot a etirely bad thig. The rage of approaches available to you ad your database admiistrator gives you a great deal of flexibility whe implemetig SQL Server HA for your SharePoit eviromet, ot oly i how you cofigure a specific procedure but also because you have the ability to combie procedures to overcome their idividual deficiecies. Regardless of how you make your SQL Server databases highly available, you should seriously reflect o the possibility of implemetig them i your eviromet. If the cotet i your SharePoit farm is busiess critical, irreplaceable, or uique, you should do everythig you ca to protect it. If your users deped o your SharePoit sites to always be available ad caot perform their work without SharePoit, you eed to make sure it is olie whe they eed it.

257 240 SharePoit 2010 Disaster Recovery Guide Now that you have SQL Server HA uder your belt, see if you ca cofidetly aswer the followig questios about SQL Server HA. You ca fid the aswers to these questios i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at courseptr.com/dowloads. 1. How may servers ca receive a sigle database s trasactio logs via log shippig? 2. What are the hardware requiremets of database mirrorig? 3. What resources must you cofigure to eable automatic failover of a mirrored database? 4. Ca you ame the editios of Widows Server 2008 that iclude failover clusterig? 5. What SharePoit compoets ca you iclude i a database istace hosted o a failover cluster?

258 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore I This Chapter Gettig Started A Overview of Backup ad Restore Capabilities Backup/Restore Prerequisites ad Cosideratios Backig Up from Cetral Admiistratio Restorig Withi Cetral Admiistratio Admiisterig a iformatio techology (IT) platform is a difficult ad sometimes thakless task. A commo complait of the IT professioal is that o oe otices whe everythig is workig as it should; it is oly whe somethig breaks or shuts dow that the professioal receives attetio. SharePoit is o differet i that regard. Whe your SharePoit eviromet is up ad ruig smoothly, it is the cotets of the documet libraries or the meetig workspaces that get all the attetio util somethig breaks ad those documet libraries ad their precious cotets become uavailable. At that poit, you as a admiistrator are goig to be oticed. Someoe is goig to wat to kow what you are doig to brig their collaboratio site back olie, ad you eed to be ready. The good ews is that every editio of the latest versio of SharePoit is shipped with built-i admiistrative tools desiged to back up ad restore your SharePoit sites, databases, ad eve farms. This chapter covers the first of SharePoit s two built-i backup ad restore toolsets specifically for admiistrators: the Cetral Admiistratio site s Backup ad Restore sectio. It demostrates how to create backups with the Cetral Admiistratio site s tool, reveals what the tool ca back up, ad discusses how to restore backups. After fiishig this chapter, you should have a workig uderstadig of the Cetral Admiistratio site s tool s prerequisites, activities, outputs, ad results. Although Microsoft has doe quite a bit for SharePoit admiistrators by icludig a umber of useful backup ad restore tools i SharePoit, we recogize that kowig how ad whe to use each tool ad apply each cocept ca be a challege. This chapter is desiged to help you specifically with the Cetral Admiistratio site s powerful backup ad restore tools. I the bous 241

259 242 SharePoit 2010 Disaster Recovery Guide chapter foud o the Cegage Learig Web site at we also apply the cocepts ad iformatio preseted here with iformatio from the other chapters i the form of disaster recovery case studies. The case studies offer a opportuity to see how you ca use the Cetral Admiistratio tools discussed here i cojuctio with the other SharePoit disaster recovery tools you have at your disposal. The visual examples provided i this chapter were geerated i a testig eviromet usig the followig platforms ad compoets. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 Stadard Editio with Service Pack 1 (SP1, build ) Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 Cliet Web browser. Iteret Explorer 8 (versio ) SharePoit. SharePoit Server 2010 Trial (Beta) with Eterprise Cliet Access Licese (build 4536) This chapter also assumes that you possess access to your SharePoit farm s Cetral Admiistratio site, a uderstadig of how to actually ope ad avigate to the site via browser, ad access to the rights ad resources ecessary to use its backup ad restore tools. Gettig Started Whe it comes to admiisterig a SharePoit farm usig a Web browser, the Cetral Admiistratio site is a admiistrator s oe-stop shop. This holds true for workig with SharePoit s backup ad restore fuctios i a friedly ad iteractive way. I fact, all the backup ad restore tools withi SharePoit 2010 s Cetral Admiistratio site are coveietly orgaized ad ca be accessed through oe page withi the site. Note: The examples that follow utilize a fictitious farm hosted o a server amed SPDEV. The Cetral Admiistratio site for the farm has a base URL of Simply substitute your farm s Cetral Admiistratio site URL i place of i the examples show throughout the rest of the chapter to follow alog where desired. Figure 9.1 illustrates the primary poit of etry to Backup ad Restore fuctioality withi the Cetral Admiistratio site. For the sake of simplicity, we refer to this page simply as the Backup ad Restore page for the remaider of the chapter. Take a momet to familiarize yourself with the appearace ad liks show, because the Backup ad Restore page is the poit of etry for each settig ad operatio discussed throughout this chapter.

260 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 243 Figure 9.1 The Cetral Admiistratio site Backup ad Restore page. You ca access the Backup ad Restore page through either or both of the followig two routes: Through the Backup ad Restore Quick Lauch lik alog the left side of ay Cetral Admiistratio page By avigatig directly to the backups.aspx page ( Before divig headlog ito Cetral Admiistratio, you eed to kow this: the bulk of your true disaster recovery plaig efforts probably are t goig to revolve aroud Cetral Admiistratio at least for backup plaig. Oe limitatio that cotiues to exist with Share- Poit s Cetral Admiistratio site is its lack of fudametal schedulig ad automatio capabilities. Cetral Admiistratio is a woderful tool for iteractively coductig backups ad restores, but you caot script it. For this reaso, most disaster recovery plas employ automated scripts ad job schedules for the SQL Server backup techiques discussed i Chapter 7 ( SQL Server 2008 Backup ad Restore ) ad the PowerShell commad lie capabilities that are covered i Chapter 10 ( SharePoit 2010 Commad Lie Backup ad Restore: PowerShell ). This does t mea that Cetral Admiistratio is useless. As this chapter demostrates, it s a fatastic tool for creatig targeted, o-demad backups i a iteractive fashio. May admiistrators also prefer a visual iterface whe restorig data, adjustig backup settigs, ad more. Regardless of prefereces, you ca view the Cetral Admiistratio site as simply aother tool i your admiistrative toolbox. A Overview of Backup ad Restore Capabilities The Cetral Admiistratio site allows you to work with SharePoit i a visual ad iteractive way. Whe you cut past the Web pages ad liks, though, the Cetral Admiistratio site is a wrapper aroud fuctioality that is exposed through the methods, properties, ad evets of key

261 244 SharePoit 2010 Disaster Recovery Guide SharePoit object model types. This is true of the PowerShell cmdlets described i the ext chapter as well. The differeces betwee Cetral Admiistratio ad the PowerShell cmdlets have less to do with fuctio tha they do with the form through which their commo uderlyig fuctioality is exposed. Both Cetral Admiistratio ad PowerShell provide differet mechaisms ad optios for carryig out disaster recovery operatios, but they are both employig the same object model types for the actual grut work behid the scees. Whe it comes to backig up ad restorig your SharePoit eviromet, it helps to kow a little bit about what is goig o uder the hood, so to speak. Do t worry, though: this chapter is t goig to become a lesso o the SharePoit object model. Chapter 11, SharePoit 2010 Disaster Recovery Developmet, speds more time lookig at the object model sectios that are relevat to disaster recovery. I this chapter, oly a light spriklig of the SharePoit iterals are icluded to provide some cotext ad facilitate uderstadig. Geerally speakig, the backup ad restore capabilities of the Cetral Admiistratio site fall ito two broad categories, ad these are preseted to you o the Backup ad Restore page as Farm Backup ad Restore ad Graular Backup. This chapter also looks at the special case of the Cofiguratio-Oly Backup, because its itet ad usage patters differ from what might be cosidered traditioal backup ad restore. Farm Backup ad Restore Full coverage is a phrase that we all like to hear whe shoppig for isurace, ad it is the best way to thik about the capabilities that are supplied through the Farm Backup ad Restore liks o the Backup ad Restore page. Backups of this type are commoly called catastrophic backups. That is the term that is employed throughout the rest of the chapter. These backups typically afford you the greatest coverage of ay out-of-the-box SharePoit optios. What Catastrophic Backups Iclude You ll ofte hear catastrophic backups i SharePoit referred to as full farm backups, but iterestigly they really are t. Before we get ito what is t icluded i them, let s talk about the objects that are available for catastrophic backup, usig the SPDEV example farm. As you ca see i Figure 9.2, a catastrophic backup is capable of capturig ad protectig a variety of the critical targets withi a farm. I geeral, the targets that ca be captured by a catastrophic backup fall ito oe of three categories, ad these categories are orgaized hierarchically. 1. Farm. A SharePoit farm is a backup target, ad it is ormally the backup target at the top of the hierarchy. I additio to havig its ow cotet (the farm cofiguratio database), the farm is a cotaier for all other objects that ca be targeted for backup withi the eviromet. 2. Services ad Service Applicatios. May of the platform capabilities that SharePoit provides are drive by some form of service or Service Applicatio. The Search Service,

262 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 245 Figure 9.2 Farm backup targets i catastrophic backup mode. IfoPath Forms Services, ad Maaged Metadata Service are examples that fall ito this category. The iformatio that is captured i a backup of this type of object differs from Service Applicatio to Service Applicatio, but it commoly icludes settigs ad ay data that is stored i associated databases. 3. Web applicatios. I the hierarchical sese, Web applicatios are the childre of SharePoit s Cotet Web Service. Whe targeted for backup, a Web applicatio carries with it ay cotet databases that are associated with the Web applicatio. I additio, a backup icludes IIS applicatio pool ad bidig iformatio, service accouts, alerts, maaged paths, web.cofig chages (if made through the SharePoit object model or Cetral Admiistratio), autheticatio settigs, ad sadboxed solutios that are associated with the Web applicatio. Whe a catastrophic backup is performed through the Cetral Admiistratio site, selectio of ay target automatically icludes all subordiate targets i the backup hierarchy. For example, selectig a Web applicatio automatically icludes all cotet databases ad settigs associated with that Web applicatio. At the highest level i the hierarchy, selectig the top-level farm target captures all targets withi the farm. You caot alter this behavior. Cautio: Pay close attetio to what is ad is ot i a catastrophic backup you perform. If you choose to perform somethig other tha a full farm catastrophic backup of your eviromet, you may uitetioally exclude items that you eed for a successful restore. For example, you caot back up may Service Applicatios without performig a full farm catastrophic backup. Services ad Service Applicatios that ca be backed up idividually ofte have a service proxy associated with them that does ot get backed up

263 246 SharePoit 2010 Disaster Recovery Guide whe oly the service or Service Applicatio is selected. As aother example, your farm s cofiguratio database is backed up oly whe a full-farm catastrophic backup is executed. These are some of the reasos for executig full farm catastrophic backups uless you are costraied by storage space or have a specific selective compoet backup sceario you are attemptig to address. The cotets of a full farm catastrophic backup are flexible ad ca be used to restore ot oly the full farm, but idividual subordiate elemets such as specific Service Applicatios ad cotet databases. What It Does t Iclude As is commo with isurace, full coverage does t come without some fie prit that you eed to read ad a variety of limitatios you eed to uderstad. I the case of catastrophic backups, full coverage is oly complete i the sese that it covers all elemets specifically withi the boudaries of SharePoit. The precedig chapters have discussed how SharePoit caot exist i a vacuum. SharePoit relies heavily o the services ad fuctioality of may systems, icludig SQL Server, Widows Server, IIS, ad a host of additioal systems. May of these systems are service providers for SharePoit, but SharePoit itself is t aware (or should it be) of how these platforms implemet or provide their services. This also meas that a SharePoit catastrophic backup caot capture settigs ad data eeded to restore these exteral systems i the evet of a disaster. Eve if you execute a full farm catastrophic backup, the followig are some of the more commo settigs ad data that backup does ot capture: Applicatio pool accout passwords HTTP compressio settigs Time-out settigs Custom Iteret Server Applicatio Programmig Iterface (ISAPI) filters Domai membership for the server IP security (IPsec) settigs Network Load Balacig (NLB) settigs Secure Socket Layer (SSL) certificates Dedicated IP address settigs SharePoit itegrated SQL Server reportig ad aalysis services databases Maual chages to ay web.cofig file Decetralized customizatios (see Chapter 5, Widows Server 2008 Backup ad Restore )

264 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 247 Just because a full farm catastrophic backup does t cover these items does t mea you caot capture them with a backup. May of these items ad targets were discussed i Chapter 5, ad techiques do exist to protect them. You simply caot rely o a SharePoit full farm catastrophic backup to do the job for you. Whe it comes to catastrophic backup limitatios, a umber of additioal items are worth metioig: Service Applicatio cofiguratio data. Just because a Service Applicatio is selected for catastrophic backup does t mea that all of its cofiguratio data is captured. I the case of the Secure Store Service Applicatio, for istace, a passphrase is supplied at the time that the Service Applicatio is cofigured. The passphrase is used to provide access to a Master Key that is used i the ecryptio of credetial sets. Backig up the Secure Store Service Applicatio does ot backup the passphrase; you must save ad protect the passphrase whe you cofigure a Secure Store Service Applicatio istace ad have the iformatio available if a restore must be performed. The Secure Store Service Applicatio is probably the most commo example of cofiguratio iformatio that is t automatically captured, but others may exist. At some poit i your backup plaig, you should review each of the Service Applicatios you use i your farm ad compile iformatio like passphrases, credetials, ad other iformatio that must be tracked ad made available for restore scearios. Remote Biary Large Object (BLOB) Storage, or RBS. SharePoit s default actio is to store images, documets, ad other file types as BLOBs withi SQL Server. Whe BLOBs are stored i cotet databases i this maer, they are captured whe a catastrophic backup is ru provided the cotet databases are selected for backup iclusio. If the SQL Server s BLOB storage behavior is altered through the use of a RBS provider other tha the FILE- STREAM provider, a catastrophic backup does ot capture BLOB cotets whe it is ru. I such a situatio, you must employ some other form of backup to esure that all associated BLOB data is protected. SQL Server Trasparet Data Ecryptio (TDE). SharePoit 2010 ca perform catastrophic backups of SQL Server databases that leverage TDE, but SharePoit does ot capture the database ecryptio key (DEK) ad other ecryptio compoets durig the process. It is your resposibility to maually back up ad restore TDE compoets, such as the DEK, a sigig certificate, ad the private key associated with the sigig certificate. Failure to capture these compoets may block your ability to make decrypted data available i restore scearios. Busiess Coectivity Services (BCS). BCS is typically employed whe SharePoit eeds to iteract with other lie of busiess (LOB) data systems such as exteral relatioal databases, customer relatioship maagemet (CRM) systems, custom Web services, ad virtually ay other o-sharepoit system housig data of iterest. Although a catastrophic backup ca capture cofiguratio iformatio (such as exteral cotet type defiitios)

265 248 SharePoit 2010 Disaster Recovery Guide defiig how SharePoit iteracts with these exteral data systems, it caot capture ay of the actual busiess data housed withi the systems. Protectio of such data must be pursued separately ad represets a differet target or set of targets i the disaster recovery sese. The precedig list of items describig what ca ad caot be icluded i a catastrophic backup is far from the last word. Because you ca exted the catastrophic backup system through custom code ad third-party products, the list of targets that ca be covered i your eviromet could be larger. If you ve read all the previous chapters, you should recogize the eed to test ay backup ad restore pla before ever havig to rely o it. Such tests help you to idetify the coclusive list of what actually ca ad caot be covered by a catastrophic backup i your eviromet. Examiig the Catastrophic Backup Files Whe you execute a catastrophic backup, you might be surprised to discover all the folders ad files that are placed i the backup destiatio. I practice, a catastrophic backup is far from a straight file geeratio process. Uderstadig the files that costitute a catastrophic backup set ca help you maage those files ad aid i your uderstadig of the backup process. Durig catastrophic backup executio, the backup set that is geerated cosists of several files ad directories. See Figure 9.3 for a example of a backup storage directory cotaiig the results of several catastrophic backup operatios. Specifically at the root level of that locatio, you fid two items related to that completed backup: a file called spbrtoc.xml ad at least oe directory amed spbrnnnn. (NNNN desigates a sequetial four-digit hexadecimal umber that Figure 9.3 File ad directory structure for a catastrophic backup locatio.

266 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 249 SharePoit uses as a uique umeric idetifier for your backup files.) SharePoit automatically icremets the NNNN umber as you save additioal backups to this directory, startig at If you chage your target backup locatio to a ew directory, SharePoit starts the umeric idetifier back at spbrtoc.xml is a XML file storig the history iformatio for the catastrophic backups stored i the target file locatio. Note: spbrtoc.xml s file ame is a acroym for SharePoit Backup Restore Table of Cotets. If you chage your target backup file storage locatio i the future, SharePoit creates a ew spbrtoc.xml i that locatio as well. Cautio: Avoid maually updatig or modifyig the files i your catastrophic backup set. This actio ca potetially corrupt your backup files ad lead to problems durig a restoratio. Microsoft does ot support writig to, movig, deletig, or reamig ay of the files i a SharePoit catastrophic backup set. spbrtoc.xml (show i Figure 9.4) cotais SPHistoryObject childre uder the top-level SPBackupRestoreHistory elemet. Oe SPHistoryObject appears for each catastrophic backup set stored i the backup locatio, ad the SPHistoryObject elemets are ordered from most recet to oldest. The spbrtoc.xml file also cotais etries for each restore operatio ru usig the catastrophic backup sets that are stored i the backup locatio. Each SPHistoryObject cotais the followig child elemets describig the backup set: Figure 9.4 A example of the cotets of spbrtoc.xml.

267 250 SharePoit 2010 Disaster Recovery Guide SPId. This is a globally uique idetifier (GUID) that SharePoit geerates automatically for the backup set. SPParetId. If the SPHistoryObject is the child of aother SPHistoryObject, this elemet is preset ad populated with the SPId GUID of the paret. This elemet typically ties a differetial backup to its paret full backup. SPRequestedBy. Displayed i DOMAIN\User format, this is the SharePoit admiistrator who submitted the backup request. SPBackupMethod. Optios are Full or Differetial. SPRestoreMethod. Optios are Noe, Overwrite, or New. Noe idicates that the backup has ot yet bee restored. Overwrite idicates that the Same Cofiguratio optio was used to restore the backup, ad New similarly maps to the New Cofiguratio restore optio. SPStartTime. This is the date ad time that the backup process was iitiated, displayed i MM/DD/YYYY HH:MM:SS format. The time is displayed i Coordiated Uiversal Time (UTC), ot the local time zoe of the server. SPFiishTime. This is the date ad time that the backup process completed, displayed i MM/DD/YYYY HH:MM:SS format. The time is displayed i UTC, ot the local time zoe of the server. SPIsBackup. Optios are True or False. If the etry i the file is for a backup, this value is True. If the etry is for a restore, this value is False. SPCofiguratioOly. Optios are True or False. Whe both cotet ad cofiguratio settigs are backed up, this value is False. If cofiguratio settigs are backed up without cotet, this value is True. SPBackupDirectory. This is the Uiversal Namig Covetio (UNC) path to the folder cotaiig the files that make up the backup set. SPDirectoryName. This is the ame of the folder (relative to the spbrtoc.xml file) cotaiig the files for the backup package. SPDirectoryNumber. This is the sequetial umber assiged to the backup package. The first package i the directory has a value of 0 (zero). SPTopCompoet. This is the top-most compoet i the tree view hierarchy of the backup compoet selectio page that was checked as a target for backup. SPTopCompoetId. This is the GUID that iterally idetifies the SPTopCompoet. SPWarigCout. This is the umber of warigs geerated durig the backup process. SPErrorCout. This is the umber of errors geerated durig the backup process.

268 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 251 Withi each catastrophic backup set s specific SPBackupDirectory (see Figure 9.5 for a example), SharePoit creates umerous files that represet your selected backup targets. Figure 9.5 Some of the files that make up a catastrophic backup set. Every directory cotais the followig elemets: Oe or more.bak files. These files cotai the cotets of your selected backup compoets that come from a combiatio of the SharePoit farm ad the SQL Server databases. Figure 9.6 shows a example of the more huma-readable.bak files cotaiig serialized SharePoit object data. The other type of.bak file that is writte to the directory cotais SQL database backup iformatio. SQL Server backup files cotai biary data that begis with a recogizable TAPE marker, as show i Figure 9.7. Beyod the TAPE marker, though, the cotets of the file are t readable. spbackup.log. This text file cotais the details of what occurred durig the backup operatio that geerated the associated catastrophic backup set. Figure 9.8 shows a example of a spbackup.log file.

269 252 SharePoit 2010 Disaster Recovery Guide Figure 9.6 Serialized SharePoit object data i a sample.bak file. Figure 9.7 SQL Server database backup i aother.bak file. Note: All time stamps i this file are saved based o the local time zoe of the server hostig the Cetral Admiistratio site, ot UTC. spbackup.xml. This XML file cotais all the metadata ad settigs iformatio that was collected for each of the farm backup targets durig executio of the catastrophic backup. Figure 9.9 shows a example. Each file cotais a sigle SPGlobalIformatio ode that

270 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 253 Figure 9.8 Cotets of a sample spbackup.log file. Figure 9.9 Cotets of a sample spbackup.xml file.

271 254 SharePoit 2010 Disaster Recovery Guide cotais data o the overall backup, similar to the package s SPHistoryObject data i its associated spbrtoc.xml file. Below the SPGlobalIformatio elemet appear may SPBackupNode elemets for each of the farm compoets targetable by catastrophic backup operatios ot just the oes that were selected for backup. Upo completio of the backup, SPBackupNodes that were actually selected for backup have a descedet SPCurretPhase elemet value of Doe. Those that were ot icluded i the backup have a SPCurretPhase elemet value of NotSelected. The SPBackupNode elemets are hierarchically ested to reflect the relatioships that exist betwee the compoets associated with each elemet. I some situatios, SharePoit may create additioal files withi the backup set s directory depedig o the compoets selected for backup or subsequet actios that are take with the backup set: Oe or more folders with GUIDs for ames. Folders of this type appear if oe or more Search Service Applicatios were targeted for backup. Withi these folders exists a Cofig directory cotaiig oise ad thesaurus files ad a projects directory cotaiig the backed up Search idices for your eviromet. sprestore.log. SharePoit geerates this text file if you have used the catastrophic backup set for restore operatios. The log file cotais the details of what occurred durig the restore process usig this backup package. sprestore.xml. This file is similar i cotet ad purpose to spbackup.xml the mai differece beig that it is associated with a restore operatio ad ot a backup. Note: All time stamps i these files are saved based o the local time zoe of the server hostig the Cetral Admiistratio site, ot UTC. Whe You Should ad Should t Use It A full farm catastrophic backup offers the greatest degree of coverage for your farm of ay outof-the-box tools. This makes a full farm catastrophic backup the operatio of choice aytime you pla to itroduce sigificat chages ito your SharePoit eviromet. The followig operatios are just a few examples of those that are more comfortably performed kowig that some catastrophic backups have bee take for isurace agaist uexpected problems or failures: Applicatio of a service pack or hotfix Chages to farm topology or the farm eviromet, such as the additio of a ew farm member or the relocatio of a server

272 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 255 The additio ad deploymet of a ew solutio package (WSP) withi the farm Ay operatios that result i sigificat chages to cotet databases, such as site collectio relocatio usig the Export-SPWeb ad Import-SPWeb PowerShell cmdlets I most cases, it is desirable to capture a catastrophic backup both before ad after the operatio beig performed. Why two backups? Well, the backup that is captured before the chage provides you with a catastrophic backup set that is stable ad cosistet. You ca use it to roll back the farm or its elemets i the evet of failure followig the chage. After you have made the chage ad verified that the farm is i a stable ad cosistet state, you should take aother catastrophic backup. This backup set provides a ew baselie for the farm goig forward. This is ot immediately useful withi the cotext of the chage you made, but it is importat i that the backup becomes the first kow stable ad cosistet poit i the farm followig the chage. This is importat because it gives you a fall-back poit util you make the ext major chage to your eviromet. At that poit, the backup/apply chage/backup sequece just described is repeated. There are certaily times whe you should avoid a catastrophic backup. Executig a catastrophic backup, particularly a full farm catastrophic backup, ca place a sigificat load o your SharePoit ifrastructure. This load ca adversely impact a ed user s experiece ad other operatios withi your farm. As a resposible admiistrator, you should cosider capturig performace metrics durig catastrophic backups as they are beig performed if you do t have a solid uderstadig of how such backups impact your farm. Observig SharePoit ad SQL Servers to see how their memory, disk, ad etwork utilizatio are affected ca help you make iformed decisios regardig whe catastrophic backups ca or should be ru. As a geeral rule of thumb, ru catastrophic backups durig off hours or times of low SharePoit use wheever possible. SharePoit s catastrophic backups ca also cosume a lot of disk space, ad the platform icludes o built-i mechaism to prue or maage backup storage. If your disk space is costraied or you sped less time maagig your storage space tha you would like, you should probably thik twice about frequet use of catastrophic backups. Graular Backup The bulk of the Graular Backup fuctioality that is icluded with SharePoit 2010 was icluded i some form i SharePoit 2007, but it was ot available from withi the Cetral Admiistratio site. You could perform a site collectio backup easily with SharePoit 2007, for example, but you had to go to a commad lie ad type STSADM o backup url <YourSite surl4 -fileame <SiteCollectioBackupFileame4. With SharePoit 2010, this fuctioality is exposed withi Cetral Admiistratio alog with some brad ew capabilities.

273 256 SharePoit 2010 Disaster Recovery Guide How Graular Backup Is Differet from Farm Backup ad Restore Although the Graular Backup fuctios are exposed i the same area of Cetral Admiistratio as the Farm Backup ad Restore fuctios, they are ot the same. Uder the hood, the catastrophic Farm Backup ad Restore fuctioality that has bee discussed thus far leverages a umber of types that are cotaied withi the Microsoft.SharePoit.Admiistratio. Backup amespace of the SharePoit object model. The fuctios that are exposed by Graular Backup, o the other had, are tied to a collectio of other types that reside i a variety of amespaces. For example, the Export a Site or List optio exposes fuctioality that resides i the Microsoft.SharePoit.Deploymet amespace a area of the applicatio programmig iterface (API) that is associated with cotet deploymet, ot backup ad restore. This distictio is importat because you should t mistakely thik that the Graular Backup fuctios operate ad behave the same way that the catastrophic backup ad restore operatios do. This is especially true for export operatios that use the cotet deploymet types. Cotet deploymet operatios are ot iteded to be full fidelity, meaig that oly a subset of cotet ad property values ca be exported or imported. Backup ad restore operatios, o the other had, are full fidelity. This may seem like a mior poit, but it carries implicatios for the scearios i which you ca utilize backups ad exports. Tip: For additioal discussio ad detail regardig the differeces betwee backup/ restore ad export/import, see Chapter 11. Site Collectio Backup As its ame implies, the Site Collectio Backup allows you to back up a sigle site collectio withi a Web applicatio residig withi your SharePoit eviromet. To perform this type of backup, SharePoit executes a combiatio of database queries ad export calls to yield a sigle backup file. The backup file is commoly assiged a.bak extesio, but you ca actually assig ay extesio you would like. This file ca the be used to restore the targeted site collectio i-place or i oe or more other Web applicatios. This is the same site collectio backup that could be performed with SharePoit 2007 through STSADM.exe usig the commad lie sytax STSADM o backup url <YourSite surl4 -fileame <SiteCollectioBackupFileame4. Cetral Admiistratio i SharePoit 2010 simply wraps the site collectio selectio ad file ame specificatio withi a graphical user iterface (GUI) for more visually orieted admiistrators. Note: You ca still perform site collectio backups usig the commad lie approach i SharePoit 2010, but PowerShell is recommeded istead of STSADM. See Chapter 10 for more iformatio.

274 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 257 Prior to startig, the backup operatio temporarily sets the lock state for the site collectio to read-oly if the site collectio s lock state is either Not Locked or Addig Cotet Preveted. I such a situatio, the site collectio s origial lock state is restored upo completio of the backup. This lock state chage is made to reduce the likelihood of cotet chages durig the backup process because such chages could result i a icosistet backup. Microsoft does t recommed the use of site collectio backups with site collectios that are larger tha 85GB, but this is ot a hard limit. As your site collectios approach ad exceed 85GB, though, you would be wise to ivestigate the use of SQL Server cotet database backups or SharePoit s ative catastrophic backup fuctioality as a more appropriate alterative to site collectio backups. Note: At the time whe this book was writte, Microsoft s TechNet site icluded a specific ote statig that site collectio backups did ot iclude workflow iformatio. This ote is icorrect. Backups that are performed with the site collectio backup approach are full-fidelity ad cotai all workflow iformatio, icludig workflow history ad workflow state. The ote was origially iteded as a warig for exports that are performed with graular export operatios through types withi the Cotet Deploymet API, ot site collectio backups. Cotet Export Microsoft giveth, ad Microsoft taketh away is a good way to summarize the arrival of the Export a Site or List fuctio i Cetral Admiistratio. Although the GUI-based maifestatio of this fuctioality is ew to Cetral Admiistratio with SharePoit 2010, the capabilities existed i the previous versio of SharePoit Desiger for SharePoit With the redesig of SharePoit Desiger 2010 to make the applicatio more task orieted, however, GUI-based cotet backup ad export fuctioality was removed. Much like the Site Collectio Backup fuctio just discussed, the Export a Site or List fuctio does exactly what its ame suggests. Through a series of drop-dow selectio cotrols, you ca select a etire site collectio, a specific site, or a specific list withi a site for export to a cotet migratio package file set. The file set is commoly give a.cmp extesio, but that is t required. If o extesio is specified for the file,.cmp is assiged. You have the optio of exportig security iformatio with the package, ad you are give the optio to decide whether all or some versios of files ad lists are exported. As with the site collectio backup capability, admiistrators still maitai the ability to execute export operatios from the commad lie usig both PowerShell ad STSADM.exe. Whe You Should Use It The Graular Backup optios overlap with the catastrophic backup ad restore operatios i some places, but they are geerally iteded to complemet them. Catastrophic backup ad

275 258 SharePoit 2010 Disaster Recovery Guide restore operatios focus o the objects that exist at the macro scale above the cotet database level objects such as the farm, services, ad Web applicatios. It is best to thik of the Graular Backup fuctios as addressig those objects that exist withi or below the cotet database level, such as site collectios, Webs, ad lists. Graular Backup operatios are well suited to migratig ad movig cotet aroud, ad they are geerally preferable to catastrophic backup ad restore operatios for this purpose. Graular Backup operatios geerate a limited file set (oftetimes oly oe file of iterest), ad their output is iteded for use i cotet duplicatio efforts. Copyig cotet from oe site to aother is a much easier affair with Graular Backup tha it is with Farm Backup ad Restore optios. This flexibility comes with some costraits, though. The practical size limitatio for site collectio backups was already discussed. Graular operatios, o the other had, target oly oe object at a time, be it a site collectio, site, list, or documet library. Graular Backup operatios are also harder o SharePoit s ifrastructure resources due to their read-itesive ad processig-itesive ature. Oe of the biggest limitatios for visually orieted admiistrators, though, is the complete lack of restore optios for Graular Backups ad exports withi Cetral Admiistratio. Cetral Admiistratio provides a woderful iterface for site collectio backups ad cotet exports, but it provides o complemetary fuctioality for restores ad imports of the items that result from these actios. Admiistrators must istead tur to commad lie operatios ad Power- Shell for such activities. Cofiguratio-Oly Backup The cocept of a cofiguratio-oly backup is ew to SharePoit 2010, ad it is a direct respose to oe of the heaviest criticisms levied agaist full farm backup ad restore i previous SharePoit versios; amely, it is t possible to perform a out-of-place restore o a backed-up farm to create a cloe of it. Farm cofiguratio databases are tightly coupled to a SharePoit farm at both the logical ad physical levels due to the way server ames ad database coectio strigs are used, ad practical use cases ivolvig the restoratio of a farm cofiguratio database through ay meas are so arrow ad ucommo that they are early oexistet. Despite this fact, the desire to fid some way to make farm cofiguratio settigs portable uder SharePoit is commo. May admiistrators, for example, require a way to create copies of their productio eviromets for use i disaster recovery, testig, developmet, cotet authorig, ad other scearios. Ufortuately, platform support for this type of operatio did t exist i SharePoit I most cases, admiistrators had o practical choice but to build a ew farm each time ad reapply cofiguratio settigs through a carefully assembled script (at best) or i a ad-hoc fashio (at worst). To ease the admiistrative burde associated with these types of scearios, Microsoft itroduced cofiguratio-oly backup ad restore with SharePoit Although it is t a complete solutio itself, it does improve the situatio i this area relative to SharePoit 2007.

276 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 259 Whe a catastrophic backup is beig set up, you have the optio of backig up cotet ad cofiguratio settigs or cofiguratio settigs oly, as show i Figure Figure 9.10 Cofiguratio-oly backup settigs. For the purposes of a cofiguratio-oly restore, both of these backup types iclude the cofiguratio iformatio that is eeded if a cofiguratio-oly restore is to be performed later. Put aother way: you ca perform a cofiguratio-oly restore usig either a cofiguratio-oly backup or a catastrophic backup. The iformatio that is restored icludes the followig type of portable cofiguratio data: Ativirus settigs Iformatio rights maagemet (IRM) settigs Outboud settigs Customizatios ad solutio packages Diagostic loggig settigs Whe you perform a cofiguratio-oly restore, these portable cofiguratio items are writte to the cofiguratio database of the target farm. The target farm ca be the farm where the cofiguratio settigs were backed up usig a catastrophic backup or cofiguratio-oly backup, thus providig a mechaism for cofiguratio rollback. The target farm ca also be aother farm altogether, allowig the cloig of settigs from oe farm to aother. Ufortuately, cofiguratio-oly backup ad restore is ot a complete solutio for cofiguratio documetatio ad replicatio. It fails to capture cofiguratio data associated with a umber of critical compoets, icludig Web applicatio ad Service Applicatio settigs. For this reaso, cofiguratio-oly backup ad restore wo t remove the eed for complete farm documetatio aytime soo. It does, however, brig admiistrators oe step closer to a future that is free of maual cofiguratio trackig. Tip: Microsoft recogizes that completely documetig a SharePoit farm s cofiguratio is challegig. I a attempt to provide admiistrators with some assistace i this area, Microsoft has created a PowerShell script that does a solid job of documetig the overwhelmig majority of cofiguratio items ad settigs i the typical SharePoit farm. See techet.microsoft.com/e-us/library/ff aspx for additioal details ad the script.

277 260 SharePoit 2010 Disaster Recovery Guide Backup/Restore Prerequisites ad Cosideratios The basic cocepts associated with backup ad restore operatios are easy to uderstad. Backups capture data, ad restore operatios put that data back. The devil is always i the details, though, ad this is especially true with SharePoit s backup ad restore capabilities. Before attemptig ay form of backup or restore with SharePoit, you eed to check a umber of lie items i a rather legthy checklist. The good ews is that oce you have cofigured your eviromet properly for backup operatios, there is little else that you must cofigure to successfully coduct restore operatios. Backup Settigs Oly a hadful of high-level settigs exist for cofiguratio of catastrophic backup ad restore operatios withi Cetral Admiistratio, ad you access these through the Cofigure Backup Settigs lik o the Backup ad Restore page. Clickig this lik takes you to the BackupSettigs.aspx page, as show i Figure Figure 9.11 The default Backup ad Restore Settigs page. Number of Threads SharePoit 2010 gives you cotrol over the umber of threads that are spu-up to carry out both catastrophic backup ad catastrophic restore operatios. By default, each of these operatios is cofigured to utilize three threads durig executio. If you are t familiar with threadig, it is easiest i this sceario to equate a thread with a object that is beig backed up or restored. Specifyig three backup threads, for example, roughly traslates ito three objects beig backed up i parallel durig the executio of the backup operatio. Three restore threads, o the other had, meas that three objects at a time ca be

278 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 261 restored simultaeously. The greater the umber of threads of executio, the greater the degree of parallelism ad the faster you ca potetially process your objects for catastrophic backup or restore. So, what is to stop you from dialig your backup ad restore threads up to their maximum value of 10? First of all, there is the obvious warig o the BackupSettigs.aspx page idicatig that it could become difficult to iterpret the log files that are geerated durig the backup ad restore operatios. With 10 cocurret writers to a sigle file, the cotets are boud to appear jumbled. More importat tha jumbled log files, though, is the potetial impact that 10 threads of parallel executio carries with regard to server resources. Processig 10 objects at oce puts a sigificatly greater strai o the memory, CPU, ad disk resources of your SharePoit servers tha processig oly 3 objects at a time. I additio, streamig backup or restore data for 10 objects at oce across a etwork places a greater load o your ifrastructure if it is ivolved i the equatio. At the extreme, this extra load could simply cause thrashig at oe or more bottleeck poits o your servers ad ifrastructure, leadig to poorer overall performace istead of better. As with most dials, some amout of experimetatio is required to fid the sweet spot that allows you to maximize your catastrophic backup ad restore performace without uiteded side effects. Cosider ruig multiple backup ad restore operatios as a test, ad vary oly the umber of threads i use for each oe. While coductig these tests, pay attetio to the memory, CPU, ad disk load beig placed o each server ad ifrastructure compoet that is ivolved i the backup or restore operatio. Oce you have foud settigs that offer the desired balace of performace ad system load, lock them i ad documet them. Remember, too, that settigs are specific ad relevat oly to the eviromet i which they were tested ad measured. Backup File Locatio Your choice of catastrophic backup locatio is a importat oe. Microsoft recommeds that you use local disks wheever possible for maximum performace, ad this recommedatio is easily observed whe all elemets of the SharePoit farm, icludig SQL Server, are istalled o a sigle physical or virtual server. I the case of a all-i-oe server, local drive refereces for both SharePoit ad SQL Server poit to the same locatio o the drive-mapped storage medium. For most practical purposes, multiserver SharePoit farms that ited to leverage SharePoit s catastrophic backup ad restore capabilities must be able to reach a etwork share that is accessible through a UNC path specificatio. Microsoft also suggests that etwork shares with 1 millisecod or less of latecy betwee themselves ad the SQL Server(s) housig SharePoit cotet should perform well. Whe you select a backup file locatio o the BackupSettigs.aspx page, SharePoit does t help you with ay of the latecy-related issues described thus far. SharePoit does, however, otify you of problems ad potetial remedies if you try to specify a ivalid locatio, as show i Figure 9.12.

279 262 SharePoit 2010 Disaster Recovery Guide Figure 9.12 Selectig a ivalid backup file locatio. You ca oly accept chages by clickig the OK butto after valid settigs have bee supplied. If valid settigs caot be supplied, the oly optio is to click Cacel. Services, Accouts, ad Permissios The executio of backup ad restore operatios through Cetral Admiistratio egages quite a few movig parts. Each time oe of these operatios is attempted, a umber of differet services, file locatios, ad security cotexts ed up i the mix. Uderstadig the iteractios of these elemets is essetial to proper backup cofiguratio ad troubleshootig. Uderstadig the Security Cotext The key to uderstadig backup ad restore operatios that are iitiated through Cetral Admiistratio is realizig that little actually happes withi the security cotext of the curretly logged-o admiistrator. Istead, admiistrators cofigure ad prepare operatios, such as a backup, that are the haded off to other services for executio. The followig list of actios roughly represets the steps that are carried out whe a full farm catastrophic backup is ru: 1. You, the admiistrator, specify the parameters of the backup operatio. 2. A SharePoit Timer service backup job is created ad scheduled for oe-time executio usig the settigs you specified. 3. Durig a sweep, the Timer service begis executio of the backup job ad egages SQL Server for some of the required backup operatios. 4. Both the Timer service ad SQL Server write directly to the desigated backup area to carry out the backup. 5. Upo completio, SQL Server is disegaged ad the Timer service backup job completes. 6. The backup is fiished. I the executio of the previous steps, the oly step that actually occurs withi your admiistrative accout cotext is step 1. Each step after the first oe occurs withi the cotext of a service accout. Timer service actios are carried out i the cotext of the SharePoit farm

280 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 263 database access accout the same accout that is used as the Cetral Admiistratio site s IIS applicatio pool idetity. SQL Server actios are carried out i the cotext of the accout uder which the SQL Server database egie is ruig. This differs sigificatly from the backup ad restore operatios that are carried out through PowerShell, where your admiistrative accout cotext is the oe that is primarily utilized for SharePoit operatios. Services ad Their Accouts Esurig that the appropriate services are eabled ad possess the ecessary privileges to carry out backup ad restore tasks ca be tricky. Thakfully, Cetral Admiistratio provides some useful guidace to ease the burde of cofiguratio i this area. At the top of each backup ad restore applicatio page withi Cetral Admiistratio is a Readiess area. For each backup ad restore operatio exposed, Cetral Admiistratio alerts you to the services that eed to be ruig ad their curret state of readiess for the desired operatio. Figure 9.13 illustrates the Readiess area whe a catastrophic backup operatio is selected ad you are directed to the Backup.aspx page. Figure 9.13 The Readiess area for Perform a Backup. If either the Timer service or the Admiistratio service is t started whe you avigate to the Backup.aspx page, you receive a warig ad a red exclamatio mark istead of the check mark for the affected service(s). You ca cotiue your cofiguratio of the backup operatio, but attempts to start a backup without addressig the Readiess warigs result i a error ad failure. Note: Readiess warigs idetify the Timer service as the Microsoft SharePoit Foudatio Timer 2010 service ad the Admiistratio service as the Microsoft SharePoit Foudatio Admiistratio 2010 service. If you attempt to locate services with these ames i the Microsoft Maagemet Cosole (MMC) Services sap-i, you wo t fid them. I reality, these services appear i the Services sap-i as the SharePoit 2010 Timer service ad the SharePoit 2010 Admiistratio service, respectively. I additio to the aforemetioed services ruig, you eed to address a couple of permissio issues before carryig out a catastrophic backup or restore operatio. As metioed i the full farm catastrophic backup example earlier, both the SharePoit Timer service ad the SQL Server service read from ad write to the backup file locatio you specify. For these services to carry out

281 264 SharePoit 2010 Disaster Recovery Guide their duties, the accouts that the SharePoit Timer service ad SQL Server service ru uder must have Full Cotrol permissios o the backup file locatio for catastrophic backup ad restore operatios. If oe or both of the accouts that are associated with the services lack the permissios they require o the backup file locatio, your requested operatio will fail. Note: If your SQL Server service is cofigured to use oe of the built-i accouts such as Network Service, be aware that SQL Server presets itself to etwork resources usig the machie s computer accout ot a separate domai user accout. The access requiremets are slightly differet i the case of Graular Backup ad Restore operatios. Each of these operatios is carried out by the SharePoit Timer service aloe. SQL Server is ot ivolved, so the rights of the SQL Server service accout are t a factor. For Graular Backup ad Restore operatios, oly the SharePoit Timer service must have Full Cotrol permissios o the backup file locatio. User Accouts Eve though Cetral Admiistratio hads off the actual executio of backup ad restore jobs to service accouts, there are still some rights that you, the admiistrator, require to access ad carry out the ecessary cofiguratio steps. Graular Backup. To access Graular Backup fuctios, you require othig more tha membership i the Farm Admiistrators group. If you are t a member of the Farm Admiistrators group, it is geerally pretty obvious because you ca t access Cetral Admiistratio. Farm Backup ad Restore. The catastrophic backup ad restore fuctios that are available withi Farm Backup ad Restore require that you are a member of the local Admiistrators group o the server housig Cetral Admiistratio. If you are ot a member of the server s Admiistrators group but are a member of the Farm Admiistrators group, a couple of the Farm Backup ad Restore fuctios are still available. As Figure 9.14 illustrates, though, the critical liks to access backup, restore, ad settigs cofiguratio pages are removed via security trimmig. For compariso, see the full list of liks available to a Farm Admiistrator who is also a local Admiistrator depicted i Figure 9.1. Figure 9.14 Security trimmig of backup ad restore liks.

282 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 265 Full Backups Versus Differetial Backups Oe of the optios that is available to you whe you are preparig a catastrophic backup is whether to perform a full backup or a differetial backup. A full backup performs a complete backup of all objects you select, whereas a differetial backup oly performs a backup of the selected objects that have chaged sice the last full backup. By extesio, this meas that differetial backups ted to be smaller tha full backups a attractive cosideratio if you are tryig to make the most of your ivestmet i disk storage. As stated, differetial backups oly capture chages that have bee made to the selected objects sice the last full backup. For differetial backups to work, a full backup of the selected objects must exist as a poit of compariso to idetify what has chaged. Without a full backup as a poit of compariso, you caot perform differetial backups. If you attempt to create a differetial backup without first havig take a full backup, SharePoit simply throws up a iformative error ad aborts the operatio. Cautio: Whe mixig ad matchig full ad differetial backup types, we have a simple recommedatio: the first backup created i the file backup locatio should be a full farm catastrophic backup. If you begi with a full farm catastrophic backup, you ca subsequetly execute a differetial backup of ay farm object (icludig the full farm) without fear of potetial problems or loss. You ca ru ito trouble if you try the opposite sceario, such as executig a full backup of oly a Web applicatio followed by a differetial backup of your etire farm. SharePoit allows you to execute this sequece of backup operatios without error, but subsequet catastrophic backups, whether full or differetial, ever capture more data tha just the origial Web applicatio util you perform a full backup of greater scope. This sceario ca be cofusig ad result i uitetioal data loss if you mistakely expected the secod full farm differetial backup to cotai data for more tha just the Web applicatio that was origially captured. Usig Uattached Cotet Databases Aother iterestig additio to the toolbox of Cetral Admiistratio capabilities i SharePoit 2010 is the ability to browse ad recover data from SharePoit cotet databases that are ot attached to the farm, as show i Figure The UattachedDbSelect.aspx page show i Figure 9.15 is the etry poit to workig with uattached cotet databases, ad you ca access it easily from the Backup ad Restore page through the Recover Data from a Uattached Cotet Database lik. From this area, it is possible to browse a cotet database, back up a site collectio withi the cotet database, or export cotet directly from the database. To uderstad why this feature is so powerful, you must first uderstad some of the costraits of cotet databases ad how recovery operatios from them were hadled i the past.

283 266 SharePoit 2010 Disaster Recovery Guide Figure 9.15 Uattached Cotet Database Data Recovery page. Cotet Recovery Prior to SharePoit 2010 This chapter speds a great deal of time discussig how to hadle catastrophic backup ad restore scearios, but i reality catastrophic farm failures occur ifrequetly. O a day-to-day basis, admiistrators more commoly fid themselves faced with the problem of cotet loss i some limited form. Whether through error, uiteded or accidetal site deletio, or some other set of circumstaces, users lose cotet from withi their SharePoit sites. This type of loss does t costitute a catastrophic failure; oetheless, there is a real eed for some type of recovery from a catastrophic backup of the cotet database that housed the cotet prior to its deletio or loss. With SharePoit 2007, this type of recovery sceario preseted some specific challeges. I most of these cotet recovery scearios, the desire was t to replace the etire cotet database from backup. The goal was to simply recover a specific item, list, site, ad so o that had bee deleted. These object-level recovery scearios were possible, but they were difficult with SharePoit s ative backup/recovery ad export/import tools. Without additioal tools, you commoly executed such a recovery accordig to the followig series of steps: 1. You, the admiistrator, were otified of the lost cotet ad asked to recover it from backup. 2. You eeded to locate a backup of the cotet database that cotaied the lost cotet. The backup could take the form of a SharePoit catastrophic backup, a SQL Server database backup, or somethig else etirely.

284 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore You restored the cotet database to a separate recovery farm eviromet or at least a farm that was ot the curret productio farm. 4. After attachig the cotet database to a Web applicatio i the recovery farm, you located the object to be recovered ad exported it. Such a export was typically coducted through a STSADM.exe o export operatio. 5. The export package that was geerated from step 4 was copied to the productio farm eviromet. 6. I the productio farm eviromet, the export package was imported to the appropriate site or other cotaier usig a STSADM.exe o import operatio. 7. The recovered cotet was available for users oce the import operatio completed. The greatest pai i this sequece of steps typically cetered o the recovery farm requiremet described i step 3. Why was a etirely separate SharePoit farm eeded just to recover some cotet? The aswer, quite simply, is because two copies of the same cotet database caot be attached to the same SharePoit farm at oce. Every cotet database i SharePoit possesses a GUID that differetiates it from all other cotet databases. If you attempt to attach a cotet database possessig a specific idetifier to a farm where a database with that same idetifier is already attached, the operatio fails. I the case of a cotet database that was restored from backup uder SharePoit 2007, it was t possible to leverage the SharePoit object model (icludig the fuctioality withi the Cotet Deploymet API that is eeded for the STSADM o export operatio) to recover objects from the database without first attachig that database to a farm. The optio to first detach the existig cotet database from the productio farm was always a possibility, but it ivolved takig dow all site collectios housed i the target cotet database ot just the site collectio that was tied to the cotet recovery operatio. I most cases, the practical respose to these costraits was the use of a separate farm for recovery purposes. Cotet Recovery Improvemets i 2010 SharePoit 2010 simplifies cotet recovery efforts tremedously by allowig you to work with cotet databases ad perform object model operatios agaist those databases without requirig that the databases are attached to a SharePoit farm. This meas that a recovery farm is o loger eeded, because SharePoit 2010 ca cotiue to work with a productio cotet database that is attached to the farm at the same time it is exportig cotet from a uattached copy of the same cotet database that was restored from backup. I short, two copies of the database are preset i SQL Server, but oly oe of them is actually attached to the SharePoit farm.

285 268 SharePoit 2010 Disaster Recovery Guide Note: For the record, there is t aythig stoppig you from usig the uattached database recovery capability to back up or export data from a ormal productio database that is actually still attached to the farm. This capability is redudat with the site collectio backup ad cotet export fuctios that are built ito Cetral Admiistratio, though, so a actual usage sceario ivolvig uattached recovery from a attached database is left up to your imagiatio. Removig the eed for a recovery farm obviously saves you the cost ad overhead associated with the maiteace of a additioal SharePoit eviromet. It depeds o your specific eeds ad SharePoit eviromet, but the uattached cotet database recovery capabilities of SharePoit 2010 may also allow you to meet more aggressive recovery time objectives (RTOs) for cotet restore operatios. With SharePoit 2007, recovery farms were commoly built as virtualized eviromets that lacked the processig power ad resources of their associated productio eviromets. A fair amout of time durig cotet recovery operatios was spet locatig backups, movig them betwee eviromets, patchig the recovery eviromet to a equivalet or greater versio tha productio, ad other busy work tied to the secod farm eviromet. With the ability to execute a database restore ad cotet recovery i oe farm eviromet, much of that extra time ad overhead goes away or is at least reduced. Backig Up from Cetral Admiistratio After a discussio of all the backgroud ad techological uderpiigs, it s time for you to kick the tires o Cetral Admiistratio s backup ad restore capabilities with some operatioal walk-throughs. Full Farm Catastrophic Backup There is absolutely o doubt that the most importat backup ad restore operatio you should kow how to perform withi Cetral Admiistratio is a full farm catastrophic backup. Executig a full farm catastrophic backup provides you with the greatest variety of optios for recovery i the evet of a catastrophic failure, cotet loss, or some other ufortuate evet. The example that follows demostrates how to use Cetral Admiistratio to perform a full farm catastrophic backup ad save the resultat backup set to a etwork share located at \\BackupHost\Backups. Before you begi, esure that you are a member of both the SharePoit Farm Admiistrators group ad the local Admiistrators group o the server housig the Cetral Admiistratio site. Both the SQL Server service ad SharePoit Timer service accouts require Full Cotrol permissios to your backup locatio. I additio, esure that you are logged ito a computer that ca access the SharePoit Cetral Admiistratio site. This is ofte your ow workstatio, but i

286 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 269 some highly secure eviromets, access to the Cetral Admiistratio site may be restricted to oly a select group of servers ad workstatios: 1. Ope a browser ad avigate to the Cetral Admiistratio site. I the case of the fictitious farm described at the begiig of the chapter, the default URL of the Cetral Admiistratio site is 2. Depedig o the cofiguratio of both the SharePoit farm ad your cliet browser, you may be prompted to log ito the Cetral Admiistratio site. If you are so prompted, supply both your userame ad password. I most cases, your userame ad password are your domai logi credetials. 3. Whe the Cetral Admiistratio site loads, avigate to the Backup ad Restore page. You ca do this by clickig the Backup ad Restore lik i the Quick Lauch meu alog the left side of the page. Alteratively, you ca click the Backup ad Restore lik i the mai zoe ear the middle of the page to reach the Backup ad Restore page, as show earlier i Figure Click the Perform a Backup lik. It is the first lik uder the Farm Backup ad Restore sectio i the mai zoe of the page, ad it takes you to the compoet selectio page for backup operatios. Tip: If you do t like all the clickig aroud, you ca avigate directly to the compoet selectio page if you have the correct URL. For the fictitious farm beig used i this example, the URL is Combie your Cetral Admiistratio site s protocol ad host ame iformatio with the /_admi/backup.aspx path to costruct the appropriate edpoit URL for your farm. 5. The Backup.aspx selectio page allows you to select the compoets of your farm for catastrophic backup. Each selectable compoet i the farm has a selectio check box ext to it; placig a check mark i the box selects ay give compoet ad those compoets below it i the backup hierarchy. I additio to displayig a check i their check box, compoets that are selected for backup are highlighted i blue. Because a full farm catastrophic backup is beig performed, place a check mark i the first check box, as show i Figure Esure that each of the items uder the Readiess header displays a check mark to sigal that it is i a state that is coducive to backup. Both the SharePoit timer ad SharePoit admiistratio services o the server hostig the Cetral Admiistratio site must be started to actually carry out a backup operatio. If aother backup or restore operatio is i-process, it must complete before you ca create a ew job. 7. Click the Next butto at the bottom of the page to move to the backup optios page show i Figure 9.17.

287 270 SharePoit 2010 Disaster Recovery Guide Figure 9.16 All farm compoets selected for catastrophic backup. Figure 9.17 Selectig optios for the catastrophic backup operatio.

288 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore Select the type of backup you wat to perform, either full or differetial. If o other backup operatio has bee performed to the destiatio locatio, your oly real optio is to perform a full backup. If you attempt to perform a differetial backup without havig already performed a full backup to the backup file locatio, your backup operatio fails immediately ad a error page is displayed whe the backup is lauched. For this example, a full backup is selected. 9. Idicate whether you wat to perform a cofiguratio-oly backup with the Back Up Oly Cofiguratio Settigs optios. The Back Up Cotet ad Cofiguratio Settigs butto, which is selected by default, captures both the cotet ad cofiguratio settigs of your farm ad is the most versatile of the two backup optios. You ca use this optio to restore both cotet ad cofiguratio settigs at a later time. The Backup Up Oly Cofiguratio Settigs optio, o the other had, does ot capture cotet ad supports oly the restoratio of cofiguratio settigs. Uless you wat to specifically back up oly the cofiguratio settigs for the farm, stick with the default selectio. I this example, both cotet ad cofiguratio settigs are backed up. 10. The Backup File Locatio is prepopulated with the locatio that is set through the Default Backup ad Restore Settigs page show i Figure 9.11, but you are free to chage the locatio to suit your eeds. I most eterprise scearios, the locatio is specified usig a UNC share ame. I sigle-server scearios where SQL Server ad SharePoit coexist o the same server, you ca use a local drive path specificatio. Regardless of how the locatio is specified, esure that the locatio is correctly accessible for all the ecessary accouts ad ready for backup operatios. I the case of this example, the path \\BackupHost\Backups is specified. 11. A estimate of the amout of disk space required for the backup operatio appears below the Backup Locatio text box. Esure that the locatio selected cotais eough free space to accommodate the backup. As a rule of thumb, it is safest to add some paddig to the estimates that the Cetral Admiistratio site provides. The last thig you wat is to go through miutes or hours of a backup, oly to have it fail ear the ed of the operatio due to lack of free space. The actual amout of that paddig varies widely based o a large umber of factors; this is aother oe of those cases where it really pays to kow how your eviromet behaves. You are best served by testig your backups multiple times to establish a baselie aroud how much storage space a average backup requires. 12. Whe you are satisfied with all the backup optios, scroll dow the page show i Figure 9.17 ad click the Start Backup butto at the bottom of the page to lauch the backup operatio. Whe you click the butto, SharePoit creates ad cofigures a timer job istace with the backup optios you specified. The timer job istace is the scheduled to execute oce. Whe this process is complete, you are redirected to the Backup ad Restore Job Status page show i Figure 9.18.

289 272 SharePoit 2010 Disaster Recovery Guide Figure 9.18 The Backup ad Restore Job Status page. 13. Iitially, the status page show i Figure 9.18 is blak. The page refreshes every 30 secods, though, ad the page begis displayig usable status iformatio oce the timer job carryig out the backup operatio is started. 14. You ca track the overall state of the catastrophic backup usig the block of iformatio that appears just uder the blue Backup bad oce the timer job gets uderway. The backup status of each farm compoet appears below the geeral iformatio block. Each compoet beig backed up begis with empty Progress, Last Update, ad Failure message details. As the backup progresses ad each compoet is addressed, these fields update. Evetually, all selected compoets are backed up, ad the operatio completes as show i Figure Figure 9.19 The status of a completed full farm catastrophic backup.

290 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore The catastrophic backup operatio may take miutes or hours to complete. The amout of time it takes to fully complete depeds o may factors, icludig the size of your farm, your etwork speed, the latecy betwee your SharePoit server ad the backup locatio, ad more. 16. Whe the backup is complete, you ca review the status of each compoet that was backed up. No go back or cacel butto exists o the Backup ad Restore Job Status page. To avigate back to the other fuctios of Cetral Admiistratio, simply use oe of the liks that appears i the Quick Lauch meu o the left side of the page. 17. If you would like to review additioal detail regardig the backup operatio that completed, you ca review the spbackup.log file that is geerated i the backup set folder (i the backup file locatio). It s worth otig that because the SharePoit Timer service carries out backup ad restore jobs, you are ot required to stay o the Backup ad Restore Job Status page while the backup job executes. You are free to avigate away from the page ad carry out other operatios withi Cetral Admiistratio. SharePoit dutifully cotiues the executio of your specified operatio i the backgroud. If you later decide that you wat to check up o the status of your operatio, simply avigate to the Backup ad Restore page ad click the Check Backup ad Restore Job Status lik uder the Farm Backup ad Restore header. Note: Durig or just after the backup operatio, remember to make a ote of ay additioal cofiguratio iformatio you might eed to track ad associate with the catastrophic backup set. This icludes the Secure Store Service Applicatio passphrase if the Secure Store is i use, credetials that are supplied for accouts ad services, ad so o. You typically eed iformatio captured i this fashio if you must perform a restore operatio usig the backup set geerated. Site Collectio Backup The site collectio backup operatio is oe that admiistrators use o a daily basis. I practice, it teds to see more use for site collectio copyig ad migratio tha it does for actual site protectio. Regardless of how you ited to use it, though, the site collectio backup operatio is a good oe to have i your admiistrative toolbox. The example that follows demostrates how to use Cetral Admiistratio to perform a site collectio backup for a SharePoit team site that resides withi the fictitious farm at spdev:18480/sites/ts1. This backup operatio results i the geeratio of a sigle file called TS1.bak i the E:\Backups directory of the server hostig the Cetral Admiistratio site. Esure that you are a member of the SharePoit Farm Admiistrators group ad that the Share- Poit Timer service accout has Full Cotrol permissios to your backup locatio before

291 274 SharePoit 2010 Disaster Recovery Guide begiig. I additio, esure that you are logged ito a computer that ca access the SharePoit Cetral Admiistratio site. This is oftetimes your ow workstatio, but i some highly secure eviromets, access to the Cetral Admiistratio site may be restricted to oly a select group of servers ad workstatios. 1. Ope a browser ad avigate to the Cetral Admiistratio site. I the case of the fictitious farm described at the begiig of the chapter, the default URL of the Cetral Admiistratio site is 2. Depedig o the cofiguratio of both the SharePoit farm ad your cliet browser, you may be prompted to log ito the Cetral Admiistratio site. If you are so prompted, supply both your user ame ad password. I most cases, your user ame ad password are your domai logi credetials. 3. Whe the Cetral Admiistratio site loads, avigate to the Backup ad Restore page. You accomplish this by clickig the Backup ad Restore lik i the Quick Lauch meu alog the left side of the page. Alteratively, you ca click the Backup ad Restore lik i the mai zoe ear the middle of the page to reach the Backup ad Restore page, as show earlier i Figure Click the Perform a Site Collectio Backup lik. It is the first lik uder the Graular Backup sectio i the mai zoe of the page, ad it takes you to the Site Collectio Backup page. Tip: If you do t like all the clickig aroud, you ca avigate directly to the Site Collectio Backup page if you have the correct URL. For the fictitious farm beig used i this example, the URL is Combie your Cetral Admiistratio site s protocol ad host ame iformatio with the /_admi/ SiteCollectioBackup.aspx path to costruct the appropriate edpoit URL for your farm. 5. The SiteCollectioBackup.aspx page appears as show i Figure Site collectio backups are less complex to cofigure tha catastrophic backups, which is reflected by the fact that oly the target site collectio ad backup path are available to you for specificatio. 6. Select the site collectio you wat to back up usig the Site Collectio drop-dow selectio box. The drop-dow cotais oly oe item, Chage Site Collectio, ad selectig it opes the Select Site Collectio dialog box see i Figure Specifyig a site collectio for backup requires that you specify two pieces of iformatio: the Web applicatio that houses the site collectio, ad the site collectio itself. You must select the Web applicatio first with the drop-dow selectio box that

292 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 275 Figure 9.20 Specifyig the parameters for a site collectio backup. Figure 9.21 Select Site Collectio dialog box. appears ear the top right of the dialog box. The drop-dow selectio box cotais oly oe item, Chage Web Applicatio, ad selectig it opes the Select Web Applicatio dialog box see i Figure Whe the Select Web Applicatio dialog box opes, the curretly selected Web applicatio is highlighted ad bold. The site collectio that is goig to be backed up i this example is i the Team Site (18480) Web applicatio, so you must select that Web applicatio. The ame of each Web applicatio is actually a lik, so clickig the Team Site (18480) ame lik selects the Web applicatio ad closes the Select Web Applicatio dialog box. 9. Oce the Select Web Applicatio dialog closes, the Select Site Collectio dialog box updates to reflect the site collectios that are available for backup withi the selected Web applicatio. I this example, the team site with a URL of /Sites/Ts1 is the desired site collectio for backup. Much like the previous dialog box s ame liks, each

293 276 SharePoit 2010 Disaster Recovery Guide Figure 9.22 Select Web Applicatio dialog box. of the URLs is a lik i the Select Site Collectio dialog box. Clickig the /Sites/Ts1 lik selects the desired team site ad updates the Title, Descriptio, ad other related iformatio, as show i Figure Clickig the OK butto closes the Select Site Collectio dialog box ad returs you to the Site Collectio Backup page. Figure 9.23 Select Site Collectio dialog box followig a Web applicatio chage. 10. The Site Collectio drop-dow selectio box o the Site Collectio Backup page updates to reflect your choice i the previous step. I the case of the curret example, the site collectio targeted for backup is Specify the path for the site collectio backup file usig the Fileame text box. Because SQL Server does t require access to the backup locatio i the same way that it does for catastrophic backups, you have a bit more flexibility i where you ca place the file that is created. You ca specify the backup locatio ad file ame through either a UNC path, such as \\BackupHost\SiteCollectios\TS1.bak, or a local path such as E:\Backups\TS1.bak. The choice of UNC path or local path is ot depedet o the umber of servers i the SharePoit farm, ad you ca use a local path i a multiserver farm. I this example, the latter specificatio is supplied. 12. Each site collectio backup geerates a sigle file. If a backup file matchig the oe you ited to create already exists, you must select the Overwrite Existig File check box

294 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 277 before proceedig. If you do ot, you receive a error idicatig that you must select the check box to overwrite the file. Tip: The Site Collectio Backup page does t provide a estimate of the backup file size the same way that the catastrophic backup optios page does. Before movig forward with a backup, esure that the selected locatio has ample storage for the file that is created. If you have access to the Web aalytics reports uder the Site Settigs meu for the site collectio i questio, you ca use the Total Storage Used (MB) metric as a startig poit for estimatio. 13. Whe you are satisfied with the parameters, click the Start Backup butto to begi the site collectio backup process. Whe you click the butto, SharePoit creates, cofigures, ad schedules a oe-time Timer service job to carry out the backup operatio. You are the take to the Graular Backup Job Status page, as show i Figure Figure 9.24 Status page showig site collectio backup i-process. 14. The Graular Backup Job Status page cotais two sectios. The top sectio of the mai page area cotais the status of the curret ad previous site collectio backup operatios ad is the area of iterest here. The bottom sectio cotais the status for the cotet export operatios that are discussed ext i Exportig Cotet. The status page refreshes every 30 secods, ad the Curret Job area of the Site Collectio Backup sectio updates as the site collectio backup proceeds.

295 278 SharePoit 2010 Disaster Recovery Guide Note: While the backup is executig, Cetral Admiistratio esures that the site collectio is placed uder a Read-Oly lock to prevet cotet chages durig the operatio. Users of the site ca cotiue to read ad browse cotet, but additios ad modificatios to the cotet ad site collectio itself are ot permitted. If you do ot wat SharePoit to lock the site collectio durig backup, you must use a tool other tha Cetral Admiistratio for the operatio. 15. Whe the site collectio backup is complete, the appropriate Curret Job status area chages to No Operatio i Progress. No go back or cacel butto exists o the status page. To avigate to the other fuctios of Cetral Admiistratio, simply use oe of the liks that appears i the Quick Lauch meu o the left side of the page. As with catastrophic backups, you are t required to stay o the Graular Backup Job Status page util the backup completes. The SharePoit Timer service carries out the actual backup operatio, so you are free to coduct other operatios both iside ad outside of SharePoit Cetral Admiistratio while the backup rus. If you avigate away from the Graular Backup Job Status page, you ca easily retur to it usig the Check Graular Backup Job Status lik o the Backup ad Restore page. Remember that Microsoft does t recommed site collectio backups for use with site collectios larger tha 85GB. As your site collectio approaches ad exceeds 85GB, it s i your best iterest to fid some other way to back up, copy, or migrate your site collectios. Exportig Cotet Sometimes you eed to recover data that has bee accidetally deleted through uiteded system actio or user error. Other times, you simply eed to export a list so that you ca iclude it i a differet site or site collectio. I both of these cases, possessig a solid uderstadig of Cetral Admiistratio s export capabilities is goig to make your job quite a bit easier tha it would be otherwise. I the example that follows, a specific list titled Images ad located at PressReleases/TestSubSite/PublishigImages withi a fictitious site is exported to a file called ImagesExport.cmp. The export file is placed o a etwork share that is accessible at \\BackupHost\Backups durig the export operatio. Before you attempt to perform a export, esure that you are a member of the SharePoit Farm Admiistrators group ad that the SharePoit Timer service accout has Full Cotrol permissios to your backup locatio. Also, make sure that you are logged ito a computer that ca access the SharePoit Cetral Admiistratio site. This is ofte your ow workstatio, but i some highly

296 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 279 secure eviromets, access to the Cetral Admiistratio site may be restricted to oly a select group of servers ad workstatios. 1. Ope a browser ad avigate to the Cetral Admiistratio site. I the case of the fictitious farm described at the begiig of the chapter, the default URL of the Cetral Admiistratio site is 2. Depedig o the cofiguratio of both the SharePoit farm ad your cliet browser, you may be prompted to log ito the Cetral Admiistratio site. If you are so prompted, supply both your user ame ad password. I most cases, your user ame ad password are your domai logi credetials. 3. Whe the Cetral Admiistratio site loads, avigate to the Backup ad Restore page. You do this by clickig the Backup ad Restore lik i the Quick Lauch meu alog the left side of the page. Alteratively, you ca click the Backup ad Restore lik i the mai zoe ear the middle of the page to reach the Backup ad Restore page, as show earlier i Figure Click the Export a Site or List lik. It is the secod lik uder the Graular Backup sectio i the mai zoe of the page, ad it takes you to the Site or List Export page, as show i Figure Figure 9.25 The Site or List Export page for cotet exports.

297 280 SharePoit 2010 Disaster Recovery Guide Tip: If you do t like all the clickig aroud, you ca avigate directly to the Site or List Export page if you have the correct URL. For the fictitious farm beig used i this example, the URL is Combie your Cetral Admiistratio site s protocol ad host ame iformatio with the /_admi/siteadlistexport. aspx path to costruct the appropriate edpoit URL for your farm. 5. To begi the process of cofigurig a export, you eed to idetify the site collectio, subsite, or SharePoit list that is goig to be exported through the Site Collectio, Site, ad List drop-dow selectio boxes. The Site Collectio drop-dow selectio box is idetical to the oe that is used for site collectio backups, ad the Site ad List drop-dow selectio boxes permit further refiig of the object that will be selected for export. You ca combie the cotets of the three drop-dow selectio boxes i four ways to select cotet ad objects at differet levels withi a site collectio. Figure 9.26 demostrates the four possible combiatios applicable to the curret example. Figure 9.26 Site Collectio, Site, ad List combiatios for export. The Images list that is goig to be exported is located withi the publishig site collectio located at so the first step toward idetifyig the list for export is to select the appropriate site collectio usig the Site Collectio drop-dow selectio box. Note: The use ad operatio of the Site Collectio drop-dow selectio box is described i steps 6 through 10 of the previous Site Collectio Backup walk-through. 6. Oce the Site Collectio is chose, the ext step is to select the subsite that houses the target Images library. I this case, the relevat subsite is located at /PressReleases/TestSubSite. Selectig this subsite is simply a matter of usig the Site

298 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 281 drop-dow selectio box i much the same way that you used the Site Collectio dropdow selectio box i step 5. Rather tha selectig a site collectio, though, the object that is selected from withi the Select Site dialog box is the /PressReleases/ TestSubSite subsite URL. Oce you select the subsite, click the OK butto to lock i the choice ad retur to the Site or List Export page. 7. Whe the Site drop-dow selectio box is populated, the List drop-dow selectio box becomes selectable. This makes sese whe you cosider that it is t possible to eumerate the lists withi a site or subsite util you choose the site or subsite. I the case of the curret example, you eed to select the Images list usig the List drop-dow selectio box. With oly some slight variatios, you carry out this actio i the same way that you chose the subsite i step 6. Istead of a subsite URL, you select the Images list title. Click the OK butto to close the Select List dialog box ad retur to the Site or List Export page. 8. After you specify the list, idetify the full path for the export package you ll create. You create export packages as cotet migratio packages, commoly with a.cmp extesio. For the curret example, the Fileame text box is populated to reflect the desire to save the package to a etwork share: \\BackupHost\Backups\ImagesExport.cmp. If a export package with the same file ame already exists at that locatio, check the Overwrite Existig Files check box to overwrite the existig file ad avoid a error. 9. Determie whether you wat to iclude security related iformatio with your export package. Whe the Export Full Security check box is checked, the export package that is created cotais security iformatio such as SharePoit user ad group iformatio alog with the actual export cotet. 10. The fial optio you have available to you, Export Versios, allows you to specify the quatity of data that is exported from lists ad libraries that support versioig. All Versios is the default ad highest-fidelity optio, ad it istructs SharePoit to select all major ad mior versios for each item i a list or library that is targeted for export. The remaiig optios allow you to idicate that oly a subset of the data available should be exported. Choosig a subset of the versios available ca result i a substatially smaller export package ad quicker export times, but the ability to review ad roll back to previous major ad mior versio items at the destiatio oce the cotet is exported may be impacted. For the curret example, choose the All Versios optio to avoid the loss of previous versios. 11. With all cofiguratio parameters specified, the Site or List Export page appears, as show i Figure To begi the export process, click the Start Export butto. SharePoit proceeds to create, cofigure, ad schedule a export timer job istace accordig to the parameters supplied. You are the redirected to the Graular Backup Job Status.

299 282 SharePoit 2010 Disaster Recovery Guide Figure 9.27 Parameters specified for a export operatio. 12. The Graular Backup Job Status page is the same oe that is moitored for site collectio backup operatios. You ca see the export job that is executig uder the Cotet Export sectio i the lower half of the mai page area. The page refreshes every 30 secods; oce the export is complete, the Curret Job status chages to No Operatio i Progress, as show i Figure Figure 9.28 A completed cotet export operatio.

300 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore No go back or cacel butto exists o the Graular Backup Job Status page. To avigate to the other fuctios of Cetral Admiistratio, simply use oe of the liks that appears i the Quick Lauch meu o the left side of the page. 14. If you eed additioal detail o the export operatio, a log file is geerated where the cotet migratio package is placed. The log file carries the same base ame as the cotet migratio package, but it has a added extesio of.export.log. I the case of this example, the ame of the log file that is geerated is ImagesExport.cmp.export.log. Uattached Cotet Database Data Recovery Aside from browsig a cotet database s hierarchy of objects, the optios afforded by the uattached database recovery feature are idetical to the site collectio backup ad cotet export fuctios that have already bee covered. The differece with the uattached database recovery feature is that the database o which backup or export operatios are to be performed must be specified first. To use a uattached cotet database for site collectio backup or cotet export purposes, follow these steps: 1. Ope a browser ad avigate to the Cetral Admiistratio site. I the case of the fictitious farm described at the begiig of the chapter, the default URL of the Cetral Admiistratio site is 2. Depedig o the cofiguratio of both the SharePoit farm ad your cliet browser, you may be prompted to log ito the Cetral Admiistratio site. If you are so prompted, supply both your user ame ad password. I most cases, your user ame ad password are your domai logi credetials. 3. Whe the Cetral Admiistratio site loads, avigate to the Backup ad Restore page by clickig the Backup ad Restore lik i the Quick Lauch meu alog the left side of the page. Alteratively, you ca click the Backup ad Restore lik i the mai zoe ear the middle of the page to reach the Backup ad Restore page as show earlier i Figure Click the Recover Data from a Uattached Cotet Database lik. It is the third lik uder the Graular Backup sectio i the mai zoe of the page, ad it takes you to the Uattached Cotet Database Data Recovery page, as show i Figure Tip: If you do t like all the clickig aroud, you ca avigate directly to the Uattached Cotet Database Data Recovery page if you have the correct URL. For the fictitious farm beig used i this example, the URL is aspx. Combie your Cetral Admiistratio site s protocol ad host ame iformatio with the /_admi/uattacheddbselect.aspx path to costruct the appropriate edpoit URL for your farm.

301 284 SharePoit 2010 Disaster Recovery Guide Figure 9.29 The Uattached Cotet Database Data Recovery page. 5. The Database Server text box is iitially populated with the ame of the default cotet database for the SharePoit farm. Verify that this is the SQL Server database istace where your uattached cotet database resides. If it is t, chage the text box cotets to reflect the desired database istace. If the Database Server text box does t cotai a valid etry, a error is geerated whe SharePoit attempts to cotact the ivalid database. Note that such a error comes after a delay because the error is throw at the ed of a timeout period. 6. The Database Name text box must be populated with the ame of the cotet database you wat to attach to. Beig able to eter a valid database ame ito this text box meas that you have some kowledge of how the cotet databases are amed i SQL Server. If you are t sure of the ame of the database you wat to attach to ad have the rights to coect to SQL Server, you ca ope a SQL Server Maagemet Studio sessio to browse the list of available databases. System-geerated SharePoit cotet databases commoly begi with WSS_Cotet_. This may help you arrow your search. 7. You eed to specify the SQL Server autheticatio mechaism. The default, Widows Autheticatio, is the best selectio i the majority of cases. Whe Widows Autheticatio is selected, SharePoit attempts to coect to the specified database usig the SharePoit Timer service accout. This geerally proceeds without issue. If your SQL Server is ruig with mixed-mode autheticatio ad you have specifically cofigured your SharePoit farm to use SQL Server autheticatio, you eed to select the SQL Autheticatio optio ad specify the appropriate SQL Server user ID ad password to coect to the database.

302 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore Idicate whether you wat to browse the cotet i the database, execute a site collectio backup, or export cotet from the cotet database usig the appropriate radio buttos. 9. Click the Next butto. Assumig all database ad autheticatio parameters are correct, you are take to a page that reflects the operatio you wat to perform. I most cases, you are goig to evetually ed up executig a site collectio backup or cotet export from the uattached cotet database. Eve if you begi by browsig the cotet database, performig some actio while browsig requires that you evetually select a site collectio backup or cotet export operatio. The good ews is that the site collectio backup ad cotet export operatios proceed accordig to the walk-throughs that have already bee provided. I fact, uattached database operatios use the same admiistratio pages cited earlier for these operatios. The oly idicatio that a uattached cotet database is ivolved durig a backup or export comes i the form of a?isuattached=1 query strig parameter at the ed of each page URL. Restorig Withi Cetral Admiistratio The flipside of backup is restore, ad carryig out restore operatios is oe of those thigs that teds to peg the average admiistrator s stress meter. I may cases, restore operatios are beig carried out uder duress ad o a tight timelie; give these facts, it makes sese that you should practice them whe you have the opportuity. As you repeatedly execute restore operatios, you get better, more efficiet, ad ultimately more comfortable with them. May admiistrators prefer Cetral Admiistratio for restore operatios simply because it teds to offer a better ed user experiece compared to commad lie operatios. Selectio of restore targets teds to be much easier, quicker, ad less error proe whe doe through a GUI. Cetral Admiistratio also provides quite a bit of feedback at each step of a restore; this feedback ca reassure ad help i troubleshootig measures if somethig does go awry. Restorig a Full Farm Full farm restoratio is usually associated with the disaster sceario you ever wat to fid yourself i. If you have to restore a complete SharePoit farm from a catastrophic backup, somethig has goe very, very wrog. Note: I SharePoit 2010, you still caot use a full farm restore to cloe a etire farm. A cofiguratio-oly restore ca address this eed to a large extet, but it does t cover all the cofiguratio settigs, properties, ad items of iterest.

303 286 SharePoit 2010 Disaster Recovery Guide What a Full Farm Restore Really Is First, you eed to be aware of oe importat fact: SharePoit s full farm restore capabilities do ot support bare-metal recovery scearios. I additio, there is oe prerequisite you must address before you ca cosider a full farm recovery; specifically, the servers that are the target of the farm recovery operatio eed to already be set up as a fuctioal SharePoit farm. The farm also eeds to be ruig a versio of SharePoit that matches the versio of the full farm catastrophic backup that you are goig to restore. Did you catch that part about eedig a fuctioal SharePoit farm? This may seem highly cotradictory; after all, why would you eed to create a farm to restore a farm? Does t that defeat the purpose of a full farm restore i the first place? If you thik about it for a momet, you probably realize that the aswer is o. Executig ay sort of restore operatio from the Cetral Admiistratio site requires a fuctioal farm. After all, Cetral Admiistratio does t ru as a stad-aloe site. I additio, the SharePoit catastrophic backup ad restore APIs require some form of fuctioal SharePoit istace to execute agaist. Like Cetral Admiistratio, the SharePoit APIs do t ru i a vacuum. Note: Whe you uderstad ad accept these facts ad prerequisites, you quickly realize that a full farm restore usig SharePoit s built-i tools comes with some rather hefty limitatios from a disaster recovery stadpoit. These limitatios, ad the times whe SharePoit s catastrophic restore capabilities may be realistically employed, are discussed a bit more i the bous chapter foud o the Cegage Learig Web site at I reality, a full farm restore is more appropriately thought of as a restore as much farm as possible operatio. A full farm restore is iteded to restore Service Applicatios, cotet, ad as much portable cofiguratio as possible while leavig the target restore farm itact. Full farm restores are ot iteded to completely overwrite every aspect of the farm they target. This may also help you uderstad why a full farm restore does t restore the SharePoit farm cofiguratio or Cetral Admiistratio cotet databases. Overwritig the cofiguratio database wholesale effectively destroys the target farm, whereas overwritig the Cetral Admiistratio cotet database disrupts SharePoit because the Cetral Admiistratio site is hostig the restore operatio. Executig the Full Farm Restore To perform a catastrophic farm restore from a full farm catastrophic backup that you have, esure that you are logged ito Cetral Admiistratio with a accout that is a member of the Cetral Admiistratio server s local Admiistrators group, ad execute the followig series of steps: 1. Ope a browser ad avigate to the Cetral Admiistratio site. I the case of the fictitious farm described at the begiig of the chapter, the default URL of the Cetral Admiistratio site is

304 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore Depedig o the cofiguratio of both the SharePoit farm ad your cliet browser, you may be prompted to log ito the Cetral Admiistratio site. If you are so prompted, supply both your user ame ad password. I most cases, your user ame ad password are your domai logi credetials. 3. Whe the Cetral Admiistratio site loads, avigate to the Backup ad Restore page by clickig the Backup ad Restore lik i the Quick Lauch meu alog the left side of the page. Alteratively, you ca click the Backup ad Restore lik i the mai zoe ear the middle of the page to reach the Backup ad Restore page show earlier i Figure Click the Restore from a Backup lik. It is the secod lik uder the Farm Backup ad Restore sectio i the mai zoe of the page, ad it takes you to the backup selectio page for restore operatios. 5. The Backup ad Restore History page appears as see i Figure The Backup Directory Locatio text box iitially cotais the farm s default backup file locatio, ad the backup sets that are stored at the locatio specified are show below the text box i order from the most recet backup set to the oldest backup set. Figure 9.30 The Backup ad Restore History page. Tip: If you do t like all the clickig aroud, you ca avigate directly to the backup selectio page if you have the correct URL. For the fictitious farm beig used i this example, the URL is Combie your Cetral Admiistratio site s protocol ad host ame iformatio with the /_admi/backup.aspx?restore=1&filter=1 path to costruct the appropriate

305 288 SharePoit 2010 Disaster Recovery Guide edpoit URL for your farm. Omittig the?restore=1&filter=1 query strig chages the look of the page slightly, but you are still able to perform a restore operatio, albeit i a slightly differet fashio. Leavig off the query strig is also equivalet to simply clickig the View Backup ad Restore History lik from the Backup ad Restore page. 6. Esure that the Backup Directory Locatio poits to the locatio cotaiig the catastrophic backup set you wat to use for the restoratio. If you chage the locatio i the text box, click the Refresh butto to populate the page with a list of the backup sets preset at the ew locatio. 7. Locate the catastrophic backup set you wat to use for the farm restoratio i the list that appears below the Backup Directory Locatio text box. If you have a large umber of backup sets i the locatio selected, you may fid it easier to locate the desired backup set by reviewig some of the details for each set. Figure 9.31 shows a full farm catastrophic backup with expaded details that has bee selected for restore. Figure 9.31 A backup set that is expaded ad selected for restore operatios. 8. Oce you have selected the desired catastrophic backup set, click the Next butto to advace to the Select Compoet to Restore page. 9. The Select Compoet to Restore page appears, ad it looks similar to the backup compoet selectio page show earlier i Figure The page displays the hierarchy of compoets that were available for backup i your farm whe the catastrophic backup set was created. Compoets that you ca select for the restore operatio you are

306 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 289 coductig have check boxes ext to them. Assumig that the backup set you selected o the previous page was from a full farm catastrophic backup, all compoets startig at the farm level ad proceedig dow the hierarchy should be available for selectio. If the backup set that you selected was t a full farm catastrophic backup, oly the subset of farm compoets that were captured i the backup are selectable for restore. 10. Select the check box ext to the Farm ode i the compoet hierarchy to select the etire farm for restore. All objects that are selected for restore are shaded, as show i Figure Whe you have reviewed the selected compoets ad determied that you are ready to cotiue, click the Next butto at the bottom of the page. Figure 9.32 All farm compoets selected for restore. 11. The Select Restore Optios page appears, as show i Figure Do t be alarmed if you begi scrollig dow the page ad fid it to be log ad itimidatig. If you are performig a full farm restore ad wat to brig your farm back to the state it was i at the time the backup set was created, most of the settigs o the page ca be left as is. The first thig you eed to do, though, is chage the Type of Restore selectio from New Cofiguratio to Same Cofiguratio. Makig this chage displays a dialog box warig you about compoet overwrites that occur durig Same Cofiguratio restores. Click the OK butto to accept the warig ad move o. 12. The secod task you must perform o the Select Restore Optios page is to verify each of the applicatio pool logi ames i the Logi Names ad Passwords sectio. You

307 290 SharePoit 2010 Disaster Recovery Guide Figure 9.33 The Select Restore Optios page. must also supply the password for each of the accouts associated with a applicatio pool before proceedig. The umber of accouts you must verify ad supply passwords for varies accordig to the umber of applicatio pools that were established for your cotet Web applicatios ad SharePoit s ow Service Applicatios. 13. If you wated to perform a cofiguratio-oly restore, the Data to Restore optio could be chaged from Restore Cotet ad Cofiguratio Settigs to Restore Oly Cofiguratio Settigs. Sice the restore i this example is a full farm recovery, leave the Restore Cotet ad Cofiguratio Settigs optio selected. 14. The text boxes i the New Names sectio are associated with the farm compoets that are beig restored; frakly, there ted to be a lot of them with a full farm restore. For a Same Cofiguratio restore, these text boxes are disabled. If you eeded to chage properties for oe or more of the backup compoets durig the restore operatio, a New Cofiguratio Type of Restore (specified i step 11) could be selected. Specifyig a New Cofiguratio restore allows you to do thigs like chage the SQL Server to which databases are restored, chage database ames, alter service ames, ad more. Because this example is a full farm restore usig the Same Cofiguratio, though, the text boxes remai disabled. 15. Whe you have verified your settigs o the Select Restore Optios page ad esured that o red exclamatio marks appear i the Readiess area of the page, click the Start Restore butto at the bottom of the page. SharePoit proceeds to create a timer job

308 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 291 istace, cofigure it with the restoratio parameters you specified, ad schedule the job for oe-time executio. It the redirects your browser to the Backup ad Restore Job Status page. Figure 9.34 shows the status page after the restore operatio has gotte uderway. Figure 9.34 A full farm restore i-process. 16. The Backup ad Restore Job Status page refreshes every 30 secods so that you ca track the executio of the restore operatio. Whe the restore operatio has completed, you ca review the status of each compoet that was restored o the status page. If additioal detail is desired, you ca review the log file that is geerated i the specific folder of the catastrophic backup set that was used for the restore operatio. The file cotaiig additioal restore detail is amed sprestore.log. 17. Review your farm s services ad Service Applicatios followig the restore to determie if you eed to start oe or more of them. To do this, click o the Applicatio Maagemet lik i the Quick Lauch o the left side of the page. Whe the Applicatio Maagemet page appears, click o the Maage Services o Server lik uder the Service Applicatios sectio i the mai page area. This opes the Services o Server page, as show i Figure If ay of the listed services or Service Applicatios should be ruig but are t, click o their associated Start liks uder the Actio colum to start them. At the same time, be aware that a limited subset of the services ad Service Applicatios may require some maual recofiguratio for properties ad settigs that could ot be restored from the catastrophic backup set. Probably the most commo

309 292 SharePoit 2010 Disaster Recovery Guide Figure 9.35 The Services o Server page. example of such is the Secure Store Service Applicatio. Before it fuctios followig a restore, you must supply to the Secure Store Service Applicatio the passphrase that was active (ad maually captured) whe the backup set was created. Without the passphrase, you caot decrypt ad use credetials stored by the Service Applicatio. Note: The Services o Server page i Figure 9.35 displays services for oly oe server at a time. If your farm has multiple SharePoit servers, you eed to review ad restart services ad Service Applicatios o potetially each server i the farm. You ca use the Server drop-dow box just above the Status colum to ascertai ad select the active server. 18. Fially, reestablish ay trust relatioships you eed if your farm is publishig services for other SharePoit 2010 farms to cosume or is cosumig services from aother farm. Note that establishig trusts is beyod the scope of the farm restore operatio beig coducted. For guidace o farm trust establishmet ad certificate exchages, see The process of restorig a farm from backup ca take substatial time, ad much of that time is spet i step 16. Although you do t eed to wait o the status page because the restore operatio is beig coducted i the backgroud, you are somewhat limited i other activities that you ca coduct across the farm. After all, the farm is i the process of chagig quite a bit while

310 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 293 the restore is beig performed. As a rule of thumb, it s best to avoid makig chages ad coductig operatios throughout the farm util the restore has fiished to avoid potetial restore collisios ad issues. Restorig a Cotet Database for Subsequet Uattached Recovery Operatios You ca restore idividual cotet compoets from a catastrophic backup set usig the same basic steps that were outlied for a full farm restore. The key for such restores is to select a specific compoet or group of compoets rather tha the etire farm i step 9 of the walkthrough. A slight variatio o the compoet restore theme is created whe you wat to restore a cotet database to leverage SharePoit 2010 s uattached cotet database recovery capabilities. I this sceario, the oly compoet to restore is a idividual cotet database. The twist, though, is that you caot use the Same Cofiguratio optio durig the restore. Doig so would overwrite the existig productio database. Istead, you eed to restore the cotet database usig the New Cofiguratio optio to chage the ame of the database. I the example that follows, a cotet database for the Test Publishig Site (18380) Web applicatio is restored usig a differet database ame. Before cotiuig, esure that you are logged ito Cetral Admiistratio with a accout that is a member of the local Admiistrators group o the server that houses the Cetral Admiistratio site: 1. Execute steps 1 through 7 of the full farm restore walk-through. Executio of these steps leaves you i a positio to select the backup set that is used for the restore operatio. 2. Select the catastrophic backup set that cotais the desired versio of the publishig site s cotet database. I the case of the backup sets displayed i Figure 9.31, the backup set with a top compoet of Farm\Microsoft SharePoit Foudatio Web Applicatio\Test Publishig Site (18380) is selected. 3. Click the Next butto, ad the Select Compoet to Restore page appears. The select for restore the cotet database for the Test Publishig Site (18380) Web applicatio, as show i Figure Oe detail worth otig i this example is that oly the Test Publishig Site (18380) compoet ad its subcompoets are available for selectio. This is because the Test Publishig Site (18380) Web applicatio was the oly compoet selected for catastrophic backup whe the backup set was geerated. Eve though the etire farm compoet hierarchy is displayed, you caot restore compoets if they were t actually backed up ad part of the backup set. 4. Click the Next butto at the bottom of the page to advace to the Select Restore Optios page. Compared to the Select Restore Optios page that appeared i the case of the previous full farm restore walk-through, the curret page is relatively

311 294 SharePoit 2010 Disaster Recovery Guide Figure 9.36 Specifyig the cotet database for restore. ucluttered. Because oly a sigle cotet database has bee selected for restore, oly that database s limited set of cofiguratio items is available for modificatio. 5. The itetio of this example is to restore the cotet database as a copy of the curret productio database, so esure that the New Cofiguratio optio is selected as the Type of Restore. 6. The New Names sectio gives you the optio of chagig the directory ame, database ame, ad database server for the cotet database durig restoratio. I this example, oly the ame of the cotet database is chaged to WSS_Restore_TestPublishig- Site, as show i Figure Both the target SQL Server ad the local directory o the SQL Server where the database is goig to be created remai the same. 7. Click the Start Restore butto at the bottom of the page. This results i the creatio, cofiguratio, ad schedulig of a oe-time restore job istace to carry out the selected restore operatio. You are the take to the Backup ad Restore Job Status scree. 8. The executio of the restore job may take miutes or loger to execute, ad the Backup ad Restore Job Status scree refreshes every 30 secods to keep you apprised of the progress beig made. 9. Somewhat couterituitively, the job completes but idicates failure, as show i Figure If you scroll dow the page to locate the actual Failure message, you see that the failure was caused by SharePoit s iability to attach the restored cotet

312 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 295 Figure 9.37 Alterig the cotet database cofiguratio o restore. Figure 9.38 Cotet database restore complete (but with a error). database to the farm. This is expected behavior; after all, the restored cotet database has the same idetifier as a existig productio database. Two cotet databases with the same idetifier caot be attached to oe SharePoit farm that s why SharePoit 2010 comes with uattached cotet database recovery capabilities.

313 296 SharePoit 2010 Disaster Recovery Guide 10. Eve though you ca t attach the cotet database to the SharePoit farm, it exists withi SQL Server ad is available for use as WSS_Restore_TestPublishigSite. To cotiue with a export of cotet from the database, use the ew database ame with the Uattached Cotet Database Data Recovery ad Exportig Cotet walkthroughs described earlier. Restorig a Site Collectio or Exported Cotet Ufortuately, o mechaism exists withi Cetral Admiistratio to restore a site collectio from a backup file (commoly with a.bak extesio) or import a cotet migratio package (typically oe or more files with a.cmp extesio) that was geerated through a cotet export operatio. For these operatios, you eed to see Chapter 10. Coclusio Takig the limitatios of the Cetral Admiistratio site s backup ad restore tools ito accout, it sometimes makes a lot of sese to use them to back up ad restore your SharePoit eviromet. As metioed earlier, the tool is useful for backig up your farm or compoets withi it prior to a plaed chage or update to your eviromet. For example, it is a best practice to back up SharePoit both before ad after you apply patches or hotfixes to your istalled SharePoit eviromet. The biggest reaso for this is that the majority of Microsoft updates to SharePoit do ot provide a mechaism to udo chages i the case of a error or coflict caused by the update. This is caused by SharePoit s heavy reliace o its back-ed databases to store cotet ad cofiguratio data. If a update modifies the tables or schemas of SharePoit s databases, you caot revert those chages without the loss of the data i those databases. So the oly way to recover from a error caused by a update or patch is to rebuild your SharePoit istallatio ad restore a backup of your cotet. The backup ad restore tools of the Cetral Admiistratio site ca be a valuable compoet of your chage maagemet process, allowig you to easily preserve your busiess-critical SharePoit cotet prior to a upgrade ad restore it i case complicatios arise. Aother advatage to usig the Cetral Admiistratio backup ad restore tools is the flexibility ad feedback they give admiistrators while usig them. The tool automatically eumerates the SharePoit compoets i your eviromet that are available for backup ad allows you to make your selectio through a graphical iterface rather tha the commad lie. Similarly, the tool shows the backup packages i your storage locatio ad importat historical data about those packages to assist you i selectig the proper target for restoratio. Fially, alog every step of the way, the Cetral Admiistratio site s backup ad restore tools give you the opportuity to review ad cofirm your selectios before iitiatig a operatio, a importat feature to take advatage of give the impact your actios ca have o your eviromet. Upo completig this chapter, you should feel comfortable aswerig the followig questios about the Cetral Admiistratio site s backup ad restore tools. You ca fid the aswers to

314 Chapter 9 SharePoit 2010 Cetral Admiistratio Backup ad Restore 297 these questios i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at 1. Which accouts require Full Cotrol rights to your backup locatio to perform a full farm catastrophic backup? 2. Site collectio backups should be limited to site collectios of what size ad smaller? 3. Which must come first: a full or a differetial backup? Why? 4. What is a recovery farm, ad why is it o loger eeded with SharePoit 2010? 5. What are the major drawbacks to relyig o the Cetral Admiistratio site as the oly tool for backig up your SharePoit eviromet?

315 This page itetioally left blak

316 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell I This Chapter Assumptios Settig the Stage Usig SharePoit 2010 s Catastrophic Backup Cmdlets Usig SharePoit 2010 s Catastrophic Restore Cmdlets Reviewig Your Backup ad Restore History Documetig Your Cofiguratio Graular Backup ad Restore via PowerShell Sice the iitial release of SharePoit Team Services i 2001, the primary commad lie tool available to admiistrators for cofigurig SharePoit s servers, sites, ad databases had bee STSADM.exe. However, that situatio chaged drastically with SharePoit Yes, STSADM.exe is still available for use i the commad lie, but the SharePoit product team has fully embraced Microsoft s ew commad lie shell, PowerShell, as SharePoit 2010 s commad lie admiistrative tool. STSADM.exe s operatios still work with SharePoit 2010, but a few ew operatios have bee added to it i the 2010 release from the more tha 200 operatios that were available i SharePoit Cotrast that with the well over 500 SharePoit-specific cmdlets that ow ship with SharePoit 2010, ad it s apparet where the commad lie emphasis is beig placed for SharePoit. Not oly that, but Microsoft has made it clear that PowerShell is its admiistrative commad lie tool of the future, which meas that ay ew fuctioality that it releases for SharePoit 2010 is goig to be i the form of PowerShell cmdlets, ot updates to STSADM.exe. Note: The cotet i this chapter assumes that you have a certai kowledge of Power- Shell ad uderstad its proper usage. You ll eed to be familiar with cocepts such as cmdlets (the basic commads i PowerShell that carry out specific tasks), the pipelie, ad its scriptig laguage. If you are ot yet comfortable with PowerShell, we highly 299

317 300 SharePoit 2010 Disaster Recovery Guide recommed makig it a priority, give its usefuless ad importace to SharePoit 2010 admiistratio. For more iformatio o PowerShell from Microsoft, as well as several lists of excellet cotet outside of Microsoft o PowerShell, see com/e-us/scriptceter/powershell.aspx. SharePoit 2010 s PowerShell cmdlets offer may of the same features ad limitatios as the Cetral Admiistratio site s graphical user iterface (GUI) backup ad restore tool. These iclude the requiremet for a Uiversal Namig Covetio (UNC) path for backup files, allowace for the backup of search idices, full or differetial backups, o optio to iclude Microsoft Iteret Iformatio Services (IIS) cofiguratios ad files i backups, ad the iability to clea up old or expired backup files. PowerShell s cmdlets ca create backups with the same graularity as the Cetral Admiistratio site s backup ad restore tool, ad its backups ca be restored i the same usage scearios as the Cetral Admiistratio site s GUI tool. But there are differeces betwee SharePoit 2010 s cmdlets ad the Cetral Admiistratio site, as well as distict advatages to usig the former over the latter. Oe differece betwee the backup ad restore cmdlets ad the Cetral Admiistratio site s backup ad restore tool is that PowerShell does ot rely o the SPTimer service to execute its fuctios; it rus idepedetly of that service o the target server. The Cetral Admiistratio site s tool actually uses the same fuctioality as PowerShell to ru a backup or restore, but as metioed i Chapter 9, Share- Poit 2010 Cetral Admiistratio Backup ad Restore, the Cetral Admiistratio site s backup ad restore operatios ru as timer jobs executed via the SharePoit farm s database access service accout. This meas that directly usig PowerShell s cmdlets reduces the chace of affectig the performace of other timer jobs, because it rus i its ow process o the server ad does ot immediately impact the other SharePoit processes ruig o the server. Cautio: Although backup ad restore operatios requested via the Cetral Admiistratio site are ru usig the idetity of the farm database access accout, PowerShell s backup ad restore cmdlets are ru usig the security credetials of the user ruig the PowerShell sessio used to ru the cmdlets. This meas that the accout used to ru PowerShell must be assiged the rights ecessary i the SQL Server database istace hostig the farm s databases as well as i the SharePoit farm itself to properly execute, ad dbo rights i the SharePoit databases targeted by the STSADM.exe operatio. The process for properly distributig these rights to users ruig the cmdlets is discussed later i this chapter. There are several iterestig features available with SharePoit 2010 s backup ad restore cmdlets that do ot have a equivalet capability i the Cetral Admiistratio Web site. Several of the ew backup cmdlets discussed i this chapter ca back up agaist SQL sapshots of live SharePoit databases, ot just the databases. There s also greater flexibility ad cotrol over

318 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 301 the output of the backup files that the cmdlets create, such as settig their allowed sizes ad their compressio. This level of cotrol just is t possible through the Cetral Admiistratio site; you ca oly accomplish it via the PowerShell cmdlets. The biggest advatage to usig SharePoit 2010 s PowerShell cmdlets is that they are executed via a commad lie, which meas they ca be cofigured as scheduled tasks i Widows o their ow or as part of a batch script ad ru with the Task Scheduler. You ca set them up to ru as automatic tasks that do ot require maual itervetio to ru. This is a importat compoet of properly protectig your eviromet i a disaster, ad oe ot directly offered by SharePoit out of the box without some additioal developmet ad cofiguratio by a admiistrator. Tip: To ru PowerShell scripts usig the SharePoit 2010 backup or restore cmdlets, you must cofigure the server for your scheduled tasks to properly allow those scripts to be executed. PowerShell uses somethig called a executio policy to determie how, or if, scripts ca be ru o a computer; you ca cofigure this policy dyamically to meet the eeds of your eviromet. By default, PowerShell s executio policy is set as Restricted, which meas that o custom scripts ca be ru o the server. You ca use the Get-ExecutioPolicy cmdlet to see what it is curretly set at o your server, ad the Set-ExecutioPolicy cmdlet to update it to a value that allows your scripts to ru. For more iformatio o those cmdlets, check out their PowerShell help documetatio. Obviously, the itroductio of PowerShell cmdlets specifically for SharePoit 2010 has drastically chaged the commad lie admiistratio picture compared to previous releases of the platform. I geeral, PowerShell is much more flexible, comprehesive, ad potet (see how we stayed away from the obvious powerful cliché there ad used a syoym istead?) tha what was previously possible with the Widows Commad Shell, eve before takig ito accout the beefit of SharePoit-specific cmdlets over STSADM.exe. Oe appealig side effect to this chage is that there is o loger a sigle applicatio with hudreds of obscure operatios ad iputs. With SharePoit 2010, the use of cmdlets allows admiistrative tasks to be completed with a much more readable ad comprehedible cmdlet istead of the geeralized STSADM. This makes uderstadig which cmdlet to use i a give situatio much more straightforward tha it was i previous releases of SharePoit. Although the itroductio of specific PowerShell cmdlets for specific operatios is a good thig, there s still a lot more goodess to talk about whe it comes to SharePoit 2010 s cmdlets. Microsoft has icluded i these cmdlets the etire set of backup ad restore fuctioality previously available i STSADM.exe, but it has added a great deal of ew fuctioality i those areas as well. Some of this fuctioality you leared about i Chapter 9, such as cofiguratiooly backups. However, some of it is available oly through PowerShell, such as the ability to back up the cofiguratio database ot coected to ay active SharePoit 2010 farm.

319 302 SharePoit 2010 Disaster Recovery Guide Fially, the ability to leverage some of PowerShell s core capabilities alogside SharePoit 2010 s disaster recovery-orieted cmdlets creates some excellet opportuities for you to script out deep automated coverage for your SharePoit eviromet. The ew Backup-SPFarm cmdlet allows you to back up your etire farm ad ca be combied with PowerShell s access to the file system of the server storig your backup files to archive or delete old backups, improvig your ability to maage your storage effectively. You ca ow use the Get-SPSite cmdlet to geerate a collectio of SharePoit site collectios, which you ca sed directly to the Backup-SPSite cmdlet via PowerShell s pipelie fuctioality. These are but two limited examples of what is ow possible with PowerShell ad SharePoit You ow have a vast rage of opportuities ad capabilities to protect your SharePoit 2010 farm accordig to your specific eeds ad costraits. Assumptios The visual examples provided i this chapter were geerated i a testig eviromet usig the platforms ad compoets listed ext. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Uless a specific item idicates that it is uique to SharePoit Server 2010, the features ad fuctioality covered i this chapter apply to both SharePoit Foudatio 2010 ad SharePoit Server 2010 i the same fashio. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 Developer Editio with Service Pack 1 (SP1, build ) Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 SharePoit. SharePoit Foudatio 2010 Release Cadidate 1 (build 4730) Settig the Stage Before we ca get ito the uts ad bolts of usig SharePoit 2010 s ew PowerShell backup ad restore cmdlets, it s importat to look at the thigs you eed to have i place ad uderstad to properly use PowerShell, SharePoit 2010, ad its cmdlets i your eviromet. Accessig the SharePoit 2010 cmdlets is ot somethig you ca do by simply opeig a PowerShell commad prompt, ad there are certai prerequisites that must be met to have the rights ad resources ecessary to use them properly. You also eed to be midful of several importat poits about how to properly use ad itegrate these cmdlets i your ow custom scripts. So let s examie what you ll eed to do to avoid these issues ad others like them before gettig to the meat of this chapter: the cmdlets themselves. Accessig the SharePoit 2010 Maagemet Shell O a Widows Server 2008 server with SharePoit 2010 istalled, SharePoit 2010 s PowerShell cmdlets ca be accessed two ways: via the SharePoit 2010 Maagemet Shell shortcut i the Start Meu s Microsoft SharePoit 2010 Products directory, or by loadig

320 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 303 the SharePoit 2010 sap-i (Microsoft.SharePoit.PowerShell) for PowerShell via the Add-PSSapi cmdlet. Both approaches load the same set of SharePoit 2010 cmdlets ito the curret PowerShell sessio, so you ca use them to cofigure ad admiister your SharePoit eviromet. Note: SharePoit 2010 requires PowerShell 2.0 to be istalled o the server for the product to be istalled, esurig that the features ad fuctioality ecessary to use the solutios discussed i this chapter are available by default o your SharePoit servers. I previous releases of the SharePoit platform, it was at best a challege to determie what rights a user eeded to have to ru admiistrative commads from the commad lie. It was ofte more of a blidfolded fishig expeditio through a miefield of icomplete iformatio ad half-truths. (Uless you read the SharePoit 2007 Disaster Recovery Guide we ever steered you wrog!) Well, as if the additio of PowerShell itself was t good eough, SharePoit 2010 s commad lie admiistratio story is so much better this time aroud thaks to oe specific cmdlet desiged to make the process of permissio ad rights assigmet much simpler: Add-SPShellAdmi. Every cmdlet we ll be discussig i this chapter requires that the accout used to ru it be grated rights withi the targeted SharePoit farm via Add-SPShellAdmi, so you eed to be ready to use it for ay accout you may use to ru these cmdlets. But what does Add-SPShellAdmi do? As you ca probably ifer from the ame (amig covetios for PowerShell cmdlets are discussed later i this chapter), it grats a amed user s accout admiistrative rights i SharePoit via PowerShell. Now, there are some specific thigs that the Add-SPShellAdmi cmdlet does to grat those SharePoit admiistrative rights, ad it is importat to uderstad what it does behid the scees withi your SharePoit eviromet before you just go blidly ruig it for all your admiistrative users. Add-SPShellAdmi grats targeted accouts the followig rights: SharePoit_Shell_Access database role membership. The user s logi is added to the SharePoit_Shell_Access role. (If this role does ot exist i the target database, the cmdlet creates it.) This is importat to ote, because the user s logi gais SQL Server s db_ower ad securityadmi rights i the database targeted by the cmdlet by associatig it with that SQL Server role, somethig you should ot take lightly. Database-specific rights. Add-SPShellAdmi ca target specific databases withi your farm via the Database iput parameter. If you specify a database, the user is added to a role that has those rights i the farm s cofiguratio database, the Cetral Admi site s cotet database, ad the targeted database. If you do ot specify a database, the cmdlet grats the user rights for the farm s cofiguratio database by default.

321 304 SharePoit 2010 Disaster Recovery Guide WSS_ADMIN_WPG security group membership. The user is also added to the WSS_ADMIN_WPG local security group o all servers i the farm with the SharePoit Foudatio 2010 Web Applicatio role, which grats certai admiistrative rights i IIS ad the file system of those affected servers. As you ca see, these are certaily otrivial rights withi your farm, ad oly admiistrators who you trust to use those powers properly should be added to the SharePoit_Shell_Access role. A sigle misstep with these rights ca drastically impact your eviromet, ad that s somethig we would ecourage you to impress upo ay admiistrator you place withi the role. Before coverig the various cmdlets that ca protect your SharePoit 2010 farm, it s importat to briefly examie the structure of PowerShell cmdlets ad how they are used. First ad foremost, cmdlets follow a strict amig covetio, startig with a verb describig the actio the cmdlet performs followed by a ou that describes the target of the actio. Directly followig the ame of the cmdlet is its iput parameter(s), which defies the specific coditios that the cmdlet should use whe ru. For a complete listig of the PowerShell cmdlets available with SharePoit Foudatio 2010, see ad for a similar listig for SharePoit Server 2010, see library/ff aspx. Note: PowerShell is ot case sesitive; you ca execute its cmdlets usig all caps, all lowercase, or a combiatio of the two. It does ot behave differetly depedig o the casig used. Tip: Oe icredibly useful feature of PowerShell is its built-i Get-Help cmdlet. A call to Get-Help followed by the ame of the target cmdlet displays a great deal of iformatio o the cmdlet, as well as a display of all the iput parameters you ca use whe ruig the target operatio. It s also ivaluable to add -Examples to the ed of the call, because it provides actual examples of how to use the cmdlet. PowerShell Backup ad Restore Prerequisites I additio to the rights grated via Add-SPShellAdmi, the accout you are usig to execute SharePoit 2010 s backup ad restore cmdlets, as well as the accout servig as the idetity of the SQL Server service o the SQL Istace (or istaces) hostig your farm s SharePoit database, must have the right to read from the directory used as the target storage locatio for the backup files that will be created. It must also be able to write ad update files i the directory. The cofiguratio of that target storage locatio is somewhat flexible, depedig o your Share- Poit farm s cofiguratio. If the SharePoit server you re usig to ru the cmdlets is also the

322 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 305 server hostig the farm s SQL Server database istace, you ca map the directory you use as the target storage locatio via a file system path such as C:\backups. I all other cases, a file share mapped via a UNC path, such as \\server\backups, is the oly way you ca referece the locatio whe usig the cmdlets. Shared UNC paths are the type of locatio most commoly used; separatig the farm s database istace to its ow server is a highly recommeded cofiguratio, especially for larger eviromets. Cautio: As with the Cetral Admiistratio site s backup ad restore tool, the amout of storage space available i your target storage locatio is importat to cosider before backig up your SharePoit farm with SharePoit 2010 s PowerShell cmdlets. The cmdlets do ot automatically compress files or archive older files to free up additioal space as eeded, so the ous is o your orgaizatio to esure that the selected storage locatio is large eough to hold your backup files. For more iformatio, see the Backup/Restore Prerequisites ad Cosideratios sectio i Chapter 9. Scriptig SharePoit 2010 s Backup ad Restore Cmdlets The majority of this chapter is geared toward explaiig what you ca ad ca t do with Share- Poit 2010 s backup ad restore cmdlets, but before we get to that, we wat to get you thikig about somethig else: how you ca ad should use them. The most importat use of these cmdlets you eed to be thikig about is how you ca create PowerShell scripts that iclude ad exted them, so you ca protect your farm completely, maage your farm s resources effectively, ad be cofidet that your farm is beig protected the same way each time a script is ru. As we cover each of the cmdlets to follow, we ll provide you with basic examples for how to use them, as well as (whe it makes sese) more advaced descriptios of how to itegrate each ito a effective script for protectig your SharePoit 2010 farm. Note: Keep i mid as you re readig this chapter that may of the tagible scriptig examples focus o the cmdlets that back up SharePoit 2010, ot those that restore it. The fact of the matter is this: backig up is a repeatable exercise that you have cotrol over whe ad how it executes. O the other had, restorig a backup is usually somethig you do t kow you have to do util a eed is at had ad the circumstaces ad coditios surroudig that restore operatio are impossible to predict. Now, do t let that dissuade you from scriptig a restore operatio; there are times it may make sese to do so, such as a automated process to replicate a productio farm s cofiguratio ito a testig or developmet eviromet. But i our cotext of SharePoit 2010 disaster recovery, there just is t a lot of eed for scriptig restore operatios, so we have t spet much time coverig that topic i depth.

323 306 SharePoit 2010 Disaster Recovery Guide You eed to uderstad some thigs about creatig successful scripts that use ad take advatage of these ew SharePoit 2010 backup ad restore cmdlets. Keep i mid that, although these cmdlets offer a rage of fuctioality, there are still thigs they caot do. Do t forget: these cmdlets are writte to work i both maual ad scripted situatios, so they have to be able to hadle oe-off uses just as much as they do repeated uses. This meas that your script may have to iclude some logic or processig that varies the way a give cmdlet is called based o variable circumstaces, because these cmdlets are ot capable of such behavior. The best example of this shortcomig is i the area of storage maagemet. With a oe-off use of a backup cmdlet, all you eed is a storage locatio with eough space to hold your backups. But if you re scriptig a backup process, it s a differet story. Cotiually usig the same backup locatio to store a backup, especially a full backup of a complete SharePoit 2010 farm, requires a astroomical amout of storage. It is far more likely that your script is goig to have to help you maage your storage, say by takig actios like deletig backup files older tha a certai date, ruig differetial backups o a much more regular basis tha full backups, or a combiatio of the two. Note: SharePoit backup cmdlets do help i this area somewhat by automatically savig backups ito uique directories, which ca make it easier to idetify ad classify backup files over time but still does ot directly address the issue of storage cosumptio. The type of backups you take is importat from aother perspective: the amout of time it takes to restore your backups. Although differetial backups are great for their lower use of storage, it ca take loger to restore large groups of differetial backups because you must apply each i successio to fully iclude updates to the targeted item sice its last full backup. Havig a high umber of differetial backups ca affect your ability to meet recovery time objectives (RTOs). Your script should allow for some flexibility i the schedulig ad type selectio of your backups so that you ca achieve the best possible balace betwee reducig the storage impact of your backups ad reducig the time it takes to restore those backups. Take some time to cosider whether there are items withi your farm that eed to be protected uiquely, say by backig them up o a differet schedule tha the rest of the farm, havig them stored i a differet locatio, or usig a differet set of parameter iputs. If you have a series of high-profile site collectios withi your farm, they may have a more striget set of recovery poit objectives (RPOs) ad RTOs tha the rest of the farm. You may fid that your users My Sites do ot eed to be backed up as frequetly. Perhaps you eed more graular status reportig for a complex Web applicatio that ofte has failig backups. Regardless of the reaso, make sure to take requiremets like these ito accout whe creatig your scripts. Just because you may be a IT professioal writig a admiistrative script, do t overlook the opportuity to icorporate key software developmet best practices ito your script, such as

324 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 307 error reportig, loggig, ad testig. Your SharePoit backup ad restore scripts eed to be rock solid. You eed to have complete faith i a resource you re creatig to protect your SharePoit eviromet day i ad day out, so make sure to write a script that ispires that kid of faith. First ad foremost, always test your scripts to make sure they do exactly what they re supposed to do; it is far better to take some extra time to idetify a potetial issue up frot tha to have it idetified for you i a productio eviromet durig a catastrophic failure. Itegrate loggig ad reportig ito your script, so that if there is a error, you ca be otified as soo as possible ad work to correct it. PowerShell offers the ability to commuicate i a lot of differet ways (the Widows Evet Log, , text messages via Short Message Services [SMS], ad so o), so take advatage of that. Fially, PowerShell s scriptig laguage offers you ubelievable access to a huge rage of fuctioality, code, ad tools to really ehace your scripts. Its itrisic pipelie capability allows you to sed the output of oe cmdlet directly to aother for further processig, a robust feature that simplifies a script s logic ad helps you to better maage data withi the script. It has direct access to Microsoft s.net Framework, as well as the SharePoit Object Model, allowig you to access code ad fuctioality that may ot be exposed by SharePoit 2010 s other PowerShell cmdlets. You ca also access more traditioal Widows resources such as Widows Maagemet Istrumetatio (WMI) objects, the Widows Registry itself, ad the file systems of your servers. Do t overlook ay potetial available resources that these items, ad may others, may offer you whe writig your backup scripts; they ca make your scripts more useful ad perform better whe put to good use. Usig SharePoit 2010 s Catastrophic Backup Cmdlets Now that we ve set the stage with some of the key iformatio you eed to keep i mid whe usig PowerShell with SharePoit 2010, let s take a closer look at the SharePoit 2010 s cmdlets used for or related to backig up some or all of your SharePoit farm. Backup-SPFarm Backup-SPFarm has a broad-reachig scope ad ca be put to use i a umber of versatile ways. As its ame implies, the primary use of this cmdlet is to create a backup of a etire SharePoit farm. You ca also use it to idetify idividual cotet compoets withi a farm that ca be backed up, back up those idividual compoets, or create a backup of a farm s cofiguratio settigs. Let s look at a example of how Backup-SPFarm ca make a full backup of a Share- Poit 2010 farm: Backup-SPFarm -Directory \\foo\backups -BackupMethod Full Now, this example is pretty straightforward; i it we passed the Backup-SPFarm cmdlet two iput parameters oe idicatig the directory that the backup files should be stored i, ad oe idicatig what type of backup should be created. The parameters you choose to provide with your call to Backup-SPFarm directly affect what kid of output it geerates whe ru. There are two

325 308 SharePoit 2010 Disaster Recovery Guide distict sets of parameters you ca use to call Backup-SPFarm: oe to geerate backups ad oe to idetify compoets withi a farm to back up. The followig lists highlight the available parameters for each set, as well as what data you should be supplyig for those parameters. The first parameter set we ll examie is the bread ad butter of Backup-SPFarm. It is used to create a backup of your farm or a idividual compoet withi it. The items i the list that follow describe the various parameters to call Backup-SPFarm to create that desired backup: Directory. Whe you re performig a backup with Backup-SPFarm, this parameter is required (uless the ShowTree parameter is provided; see the ext list for further iformatio). The target directory ca be o the file system if SharePoit is istalled o the same server as its back-ed database; otherwise, it must be a UNC shared directory. You ca use this directory to store multiple backups for your farm. SharePoit automatically creates child folders withi the directory to store each backup s files. BackupMethod. Whe you re performig a backup with Backup-SPFarm, this parameter is required (uless the ShowTree parameter is provided). Acceptable iput parameter values are Full or Differetial ad determie what type of backup is made for the target SharePoit compoet. For more iformatio o the differeces betwee full ad differetial backups, see the Full Backups Versus Differetial Backups sectio i Chapter 9. Remember, to complete a differetial backup with this cmdlet, you must have already ru at least oe full backup of the item you are targetig. Iterestigly, some service applicatios always require a full backup; if you use the Differetial optio whe backig up oe of these service applicatios, SharePoit still performs a full backup. AssigmetCollectio. This is a optioal parameter, iteded to allow for the proper disposal of objects. This parameter allows those objects to be assiged to a variable with a object of type SPAssigmetCollectio, which the cmdlet disposes of whe it is doe with them. For more iformatio o this importat parameter, see the SharePoit Object Disposal sidebar followig this list. BackupThreads. This parameter is ot required. It determies the umber of threads SharePoit uses to complete the backup operatio ad must be a iteger from 1 to 10. If o BackupThreads value is provided, SharePoit defaults to three threads. Note: The more threads that are used, the more compoets that ca be backed up at the same time, which has the potetial to reduce the time ecessary to complete the backup operatio. The trade-off with this is that the use of additioal threads adds more data to your backup logs ad makes them more difficult to read, because etries are etered i the order they occur with o correlatio to which thread they are related to. If you are troubleshootig issues with your backups, reducig this value to oe thread makes the log files much more readable.

326 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 309 CofiguratioOly. This is a optioal parameter that does ot actually require that a iput value be provided for it. If this switch is used, the cmdlet oly backs up the cofiguratio data for the item targeted, whether that is the full farm or a idividual compoet of that farm. For more iformatio o cofiguratio-oly backups, see Chapter 9. It is also importat to ote that you ca oly use this parameter agaist the cofiguratio data for the farm that the server hostig the sessio for the SharePoit Maagemet Shell belogs to. There is aother SharePoit 2010 backup cmdlet that provides similar fuctioality to Backup-SPFarm whe this parameter is used but is ot costraied by this restrictio to the curret farm, Backup-SPCofiguratioDatabase, which we ll cover later i this chapter. Cofirm. This is a optioal parameter. If this parameter is used with a iput value of True, the cmdlet prompts the user to cofirm that he wats to proceed with the actio. If a value of False is provided, the cmdlet proceeds without promptig for permissio oce executed. The default value for this parameter is False. Force. This is a optioal parameter that does ot actually require a iput value to be provided for it. If this switch is ot used, the cmdlet does ot proceed with the backup operatio if it estimates that there is ot eough disk space available to store the backup. If it is used, that check is overridde, ad the backup is executed regardless of how much storage is available. Item. This parameter is ot required. By default, if o item is specified, the etire farm is backed up. If a Item iput parameter is provided to specify the SharePoit compoet to be backed up, it must be a valid item i the farm. If the item has spaces i its ame, the etire item must be eclosed withi quotatio marks ( ). If the exact ame or path for the desired compoet is ot kow, you ca use the ShowTree switch to list the compoets available withi the farm. (See the followig list for more iformatio o the ShowTree switch.) This parameter allows the cmdlet to be used to protect Web applicatios, service applicatios, cotet databases, ad much more withi your SharePoit farm. Percetage. This iput parameter is ot required. If a value is specified for the Percetage iput parameter, it must be a iteger betwee 1 ad 100 ad is used to determie the frequecy with which Backup-SPFarm reports progress of the backup operatio. For example, specifyig a value of 20 displays the progress of the backup operatio for every 20 percet of the operatio that is completed. If o Percetage parameter is specified, STSADM.exe defaults to reportig progress every 5 percet of the operatio. This iput parameter has o impact o the outcome of the backup operatio; it oly affects the amout of iformatio that the cmdlet reports about its activities durig the operatio. SharePoit is ot able to calculate the percet completed of the backup operatio with 100 percet accuracy. You may fid that your actual progress updates do ot appear with exactly the requested frequecy.

327 310 SharePoit 2010 Disaster Recovery Guide Tip: For large SharePoit compoets, Microsoft recommeds that a Percetage iput of 1 be used to provide the best status data about your backup operatio. WhatIf. This is a optioal parameter. If this parameter is used, PowerShell displays a message statig what the outcome of ruig the cmdlet will be, but the cmdlet itself is ot executed. This ca be helpful whe testig scripts, allowig you to verify that you ca provide the correct set of iputs ad parameters to the cmdlet. SharePoit Object Disposal Oe thig SharePoit admiistrators must come to terms with whe usig PowerShell to work with SharePoit, regardless of whether it is for backig up, restorig, or aother actio, is overcomig a issue that SharePoit developers have bee dealig with already: object disposal. Some objects withi SharePoit s object model, such as SPWeb ad SPSite, ca require, ad more importatly, hold o to a great deal of memory whe used. You must properly dispose of them whe a applicatio is doe usig them to free up that memory. This is a challege that developers have had to tackle i SharePoit for quite some time, datig back at least to SharePoit s 2003 releases. I the past, Microsoft has made tools like the SharePoit Dispose Checker to help developers ad admiistrators idetify issues with object disposal i custom applicatios. Furthermore, Microsoft has icluded the AssigmetCollectio parameter i all of its SharePoit 2010 cmdlets as a way to reduce their potetial for risk i SharePoit 2010 PowerShell scripts. Carefully cosider usig this parameter if your call of Backup-SPFarm also ivolves usig SharePoit s SPWeb, SPSite,orSPSiteAdmiistratio objects; otherwise, it may ot be ecessary, but it is still somethig you eed to be midful of ad cosider. I geeral, SharePoit 2010 s PowerShell cmdlets expose so much more of SharePoit s ier workigs ad fuctioality that developers ormally accessed, ot just with its cmdlets but via its object model ad Web services. Because of the power of this ew access, you eed to costatly evaluate your SharePoit 2010 PowerShell scripts to avoid memory leaks ad performace issues. This ca be a major risk to your SharePoit eviromet, ad oe that we highly recommed you ivest time i learig more about. Oe great place to start that process is a outstadig blog post by SharePoit MVP Gary Lapoite o SharePoit 2010 s cmdlets. The secod half of the post is devoted to the subject ad two key cmdlets you eed to kow more about. The first cmdlet is Start-SP-Assigmet. Callig it creates a object with a type of SPAssigmetCollectio, which you ca pass to other SharePoit 2010 cmdlets usig the AssigmetCollectio parameter. The secod cmdlet is Stop-SPAssigmet.

328 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 311 Callig it disposes of the SPAssigmetCollectio object whe your script is doe. You ca fid Lapoite s post at stsadm-ad-powershell.html. The secod parameter set for Backup-SPFarm is best used to obtai valuable iformatio about your farm for backig it up, rather tha backig it up itself. The key parameter i this set is the ShowTree parameter. Its presece idicates that the secod parameter set is beig used istead of the first. ShowTree. This is a optioal parameter. If the ShowTree parameter is icluded with the call of Backup-SPFarm for a backup, the cmdlet does ot complete a backup of ay SharePoit compoets. Istead, it displays the compoets i the farm so that you ca use their ames to request a backup. If a value is specified via the Item parameter, ay compoets that are ot childre of that iput are excluded ad marked with a asterisk (*). Ay compoets that caot be backed up are eclosed withi square brackets ([ ]). See Figure 10.1 for a example of the output produced whe you use this parameter with Backup-SPFarm. AssigmetCollectio. This is a optioal parameter. It is used with this parameter set i the same way that it is i the first parameter set. Figure 10.1 A call of the Backup-SPFarm cmdlet with the ShowTree switch i the SharePoit 2010 Maagemet Shell widow, ad the output of the operatio.

329 312 SharePoit 2010 Disaster Recovery Guide CofiguratioOly. This is a optioal parameter. It is used with this parameter set i the same way that it is the first parameter set. Item. This is a optioal parameter. It is used with this parameter set i the same way that it is the first parameter set. WhatIf. This is a optioal parameter. It is used with this parameter set i the same way that it is the first parameter set. The beautiful thig about PowerShell is that most cmdlets (whe they re well desiged ad writte), do exactly what their ames say they do, ad that s certaily the case with Backup-SPFarm. It defiitely backs up a SharePoit farm. Usig the first parameter set ad the miimal set of iputs for it, you ca easily back up your etire farm: its cofiguratio, its cotets, ad its service applicatios. Whe we start to talk about the ew PowerShell cmdlets for restorig cotet ito SharePoit 2010, this becomes eve more importat, because we ca restore each of these compoets i a SharePoit 2010 farm, somethig that was ot ecessarily possible i previous versios of SharePoit. Aother importat aspect of the Backup-SPFarm cmdlet is its ability to back up idividual compoets with the Item parameter. By specifyig a sectio of your farm with the Item parameter, you ca back up ad protect it separately from the rest of your farm. If you wat to make a copy of a Web applicatio s cotet database to trasfer dow to a farm i your testig eviromet or take a exact copy of the cofiguratio of your farm s Search service applicatio for use i aother productio farm, you ca do it with the Backup-SPFarm cmdlet ad its Item parameter. The Item parameter also becomes much more potet whe you combie it with PowerShell s pipeliig ad loopig capabilities; with some clever use of the PowerShell laguage ad the Backup-SPFarm cmdlet ad its ShowTree ad Item parameters, you ca idividually protect multiple compoets withi your farm without a great deal of effort. The possibilities for how you ca use this cmdlet ad its valuable optios withi your eviromet to meet its specific eeds are quite impressive ad give you diverse ad creative optios for protectig your SharePoit farm. Do t overlook the ability to back up the data about the cofiguratio of your farm with Backup-SPFarm s CofiguratioOly parameter. This parameter highlights a ew aspect of SharePoit 2010 that was t possible i previous versios of SharePoit: backig up the cofiguratio data ad settigs for your SharePoit 2010 farm, ot just its cotets. This meas you ca capture the overall setup of your farm ad use it to re-create a farm with most of the same settigs i aother eviromet, such as a developmet farm or a disaster recovery eviromet for failover, both which are cases where havig a eviromet idetical to the productio oe ca be valuable. Iterestigly, this feature is so importat i SharePoit 2010 that it s also available via a separate cmdlet, which we ll look at i a bit. Please take ote, however, that we did ot say that the CofiguratioOly parameter makes a complete backup of your farm s cofiguratio data. That s because it does t. SharePoit 2010 s cofiguratio backups do t make a exact copy of a farm s settigs; they oly capture

330 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 313 some of its portable settigs ad cofiguratios. As we metioed i Chapter 9, this parameter does ot have the ability to iclude cofiguratio data for most of SharePoit s service applicatios or the SharePoit Web applicatios curretly existig i the farm. Now that you re familiar with Backup-SPFarm, let s look at a example of a comprehesive approach to usig that cmdlet to effectively ad flexibly back up your SharePoit 2010 farm. The PowerShell fuctio listed ext, Backup-Farm, is desiged to ot oly back up a SharePoit farm, but check its output log files for errors ad the use aother fuctio (Record-Evet) to report its fidigs. The fuctio ca be used to execute both full ad differetial backups via the $backupmethod iput parameter ad is set to target the etire farm regardless of the method provided. You ca also specify the storage locatio of the backups via a iput to allow for customizatio; the fial two iputs are solely for error reportig. Fuctio Backup-Farm ($backupmethod, $backupdir, $errorflag, $etrytype) { # Ru a farm backup with the SP2010 CMDLET usig the parameters passed i Backup-SPFarm -directory $backupdir -backupmethod $backupmethod # Get the most recetly modified backup folder $ewestfolder = (Get-ChildItem -path $backupdir Sort -property LastWriteTime Select-Object -last 1 -property FullName format-table -hidetableheaders out-strig foreach { $_.trim() } ) # Build the file path for the most recetly created backup log file $ewestlog = Joi-Path -path $ewestfolder -childpath "spbackup.log" # Gettig the umber of errors i the backups log file # (subtractig 1 for the reportig lie at the ed of the documet) $errorlog = Get-Cotet $ewestlog Out-Strig $errorcout = [regex]::matches($errorlog,"error").cout - 1 # If there is a error, report it If ($errorcout -gt 0) { # Create Error Message $evetmsg = $evetmsg + "At least oe error was foud while makig a " + $backupmethod + "backup, stored i the " + $ewestfolder + "directory. " + "Please review the spbackup.log file i that directory carefully to " + "diagose ad resolve the issue before ruig aother backup." # Report a error Record-Evet -evetmsg $evetmsg -etrytype "Error"

331 314 SharePoit 2010 Disaster Recovery Guide # Set the Error flag to "O" $errorflag = 1 } Else #Report the successful Farm backup { # Report the Deletio Evet $evetmsg = "A " + $backupmethod + " backup of the farm was successfully " + "backed up to " + $ewestfolder + ". See " + $ewestlog + " for more iformatio." Record-Evet -evetmsg $evetmsg -etrytype "Iformatio" } } Backup-SPCofiguratioDatabase As we ve already metioed, the Backup-SPCofiguratioDatabase cmdlet is aother optio you have available to back up a SharePoit 2010 farm s cofiguratio, without icludig ay of its cotets. It works much like the Backup-SPFarm cmdlet whe used with the CofiguratioOly parameter, but there are some differeces betwee that ad the Backup-SPCofiguratioDatabase cmdlet. The itet of each of these two optios is similar, ad the fuctioality that they use behid the scees is pretty much the same, but those differeces are crucial to uderstad. Whe we were talkig about the Backup-SPFarm cmdlet, you may ot have oticed it, but we were careful to say that Backup-SPFarm is for use with your farm the curret farm that the server you re ruig the cmdlet o is part of. That s the way it works; Backup-SPFarm is for use with the curret farm oly; you caot ru it agaist other SharePoit 2010 farms if the server executig the cmdlet is ot attached to them. But the costrait does ot bid Backup- SPCofiguratioDatabase; you ca ru the cmdlet agaist ay farm s cofiguratio database, as log as the server hostig the cmdlet ca coect to the database over the etwork ad you as the cmdlet s operator ca provide the proper credetials to access the database. But the most importat thig to take i about this cmdlet is that cofiguratio databases targeted by Backup-SPCofiguratioDatabase do t eve have to be used by a active farm. You ca use the cmdlet to create a backup of ay SharePoit 2010 cofiguratio database as log as that database is attached to a SQL Server istace ad ruig. Here s a example of how to call Backup-SPCofiguratioDatabase to back up a cofiguratio database i a remote Share- Poit server farm: Backup-SPCofiguratioDatabase -Directory \\foo\backups -DatabaseServer RemoteSQLIstace -DatabaseName RemoteSPCofigDB This capability may seem a little strage at first, but i reality, this is a powerful feature. It allows you to back up ay cofiguratio database, whether it s from a ruig farm, a farm you shut dow a few weeks ago, or eve a SQL Server backup of a cofiguratio database that

332 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 315 you ve brought back olie for the express purpose of capturig its farm s cofiguratio ad settigs. Oce you have that backup, there s quite a bit you ca do with it. This is aother of those situatios i which SharePoit 2010 gives you a great deal more flexibility ad fuctioality tha its previous versios. Now you ca back up a farm s cofiguratio ad have a template you ca use to deploy as may times as you wat, the same way every time. Now you ca capture the exact settigs of your farm, eve if it s ecoutered a error ad offlie, so you ca recover ot just your cotet, but the specific setup of the farm that was hostig it. Now you have a lot more ways to protect yourself from errors, corruptio, ad disaster ad recover from them more effectively. It may seem ice from a backup coverage perspective, but Backup-SPCofiguratioDatabase s ability to directly address cofiguratio databases for other farms really starts to make the most differece whe you thik about it from the restore side of the equatio. It s ot so much about targetig other active farms, because you ca always just ru the cmdlet directly i that farm. Creatig a backup straight from a cofiguratio database i SQL Server that is t associated with a live farm really allows you to protect your farm i a way that few, if ay, of the other tools discussed i this book ca. This becomes eve more impressive whe you cosider the limitatios of those other tools. Microsoft does ot support directly restorig a SQL backup of a cofiguratio database to a existig or ew SharePoit 2010 farm. The Cetral Admiistratio site ca back up a farm s cofiguratio, but you ca t schedule those backups. Eve Widows Server s Volume Shadow Copy Service (VSS), a backup techology discussed i greater detail later i Chapter 11, Share- Poit 2010 Disaster Recovery Developmet, is icapable of restorig a farm s cofiguratio data or its Cetral Admiistratio Web site. But with Backup-SPCofiguratioDatabase, you ca restore a farm s cofiguratio data with little more tha SQL Server backups of the database. This meas that it makes a lot more sese to do regular backups of your farm s cofiguratio database with SQL Server; the backups ca ow play ito a restore sceario, i much the same way that you ca use the cofiguratio database to protect your farm s cotet databases. I the evet of a disaster where you ve lost your etire farm, you ca restore a SQL Server backup of your cofiguratio database ito a SQL Server istace ad with Backup-SPCofiguratioDatabase create a SharePoit cofiguratio-oly backup of it. The you ca restore that cofiguratio data ito a ew farm with the Restore-SPFarm cmdlet. It is t goig to brig back everythig, but it does restore importat data about a farm ad eables you to get that data restored much more quickly tha other alteratives. There are may similarities betwee the Backup-SPCofiguratioDatabase ad Backup-SPFarm, such as the Item ad ShowTree parameters. They both create backup files i the same maer; they both write to the spbackup.log file; they re both Pisces (just kiddig). Really, most of the other differece betwee Backup-SPFarm ad Backup-SPCofiguratioDatabase are mechaical: they do have slightly differet iput parameters you ca use to call them. Out of those differeces, the

333 316 SharePoit 2010 Disaster Recovery Guide oly oe worth otig is that there are o differetial backups with Backup-SPCofiguratio- Database; it oly takes a full backup of a cofiguratio database. Because the best use case for Backup-SPCofiguratioDatabase is i a restore sceario i which you re oly ruig it oce ayway, this is t a big deal (ot to metio that the files geerated by the cmdlet stay pretty small). Before we dive ito the specifics of the Backup-SPCofiguratioDatabase, we wat to metio oe other differece about the two cmdlets. Whe ru with its default settigs, Backup-SPFarm uses three threads to back up a SharePoit 2010 farm; with the default settigs, Backup- SPCofiguratioDatabase oly uses two. This is a pretty mior poit (especially because you ca t cotrol the umber of threads that Backup-SPCofiguratioDatabase uses), but if you ever get ito fie-tuig the performace of your backups, you may wat to take that differece ito cosideratio so you kow that they re goig to behave differetly uless you specify the umber of threads. If you re cocered about performace, Backup-SPFarm is the oly oe of the two cmdlets that allows you to set the umber of threads used; Backup- SPCofiguratioDatabase does t offer a BackupThread parameter. To paraphrase B. A. Baracus, eough with all the jibber jabber; let s talk about the details of Backup-SPCofiguratioDatabase. The items i the list that follow describe the various parameters used to call Backup-SPCofiguratioDatabase to create a backup of a SharePoit 2010 cofiguratio database: Directory. Whe you re performig a backup with Backup-SPCofiguratioDatabase, this parameter is required (uless the ShowTree parameter is provided; see the ext list for further iformatio). The target directory ca be o the file system if SharePoit is istalled o the same server as its back-ed database; otherwise, it must be a UNC shared directory. This directory ca store multiple backups for your farm. SharePoit automatically creates child folders withi the directory to store idividual backup files. AssigmetCollectio. This is a optioal parameter, iteded to allow for the proper disposal of objects. Carefully cosider usig this parameter if your call of Backup-SPCofiguratioDatabase also ivolves usig SharePoit s SPWeb, SPSite, or SPSiteAdmiistratio objects; otherwise, it is ot likely to be ecessary. DatabaseCredetials. This parameter is ot required; you should use it oly if the accout that executes the Backup-SPCofiguratioDatabase cmdlet is ot a member of the db_backupoperator role i the SQL Server istace hostig the targeted cofiguratio database or SQL Autheticatio is used to coect to a database. The credetials provided should have admiistrator rights i SQL Server. If this parameter is ot provided ad required, the cmdlet prompts the user for the userame ad password values. DatabaseName. This is a optioal parameter that does ot actually require that a iput value be provided for it. If this parameter is used, the cmdlet backs up the cofiguratio

334 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 317 database specified. If o value is supplied for this parameter, the cmdlet defaults to selectig the cofiguratio database for the farm that the SharePoit 2010 server hostig the cmdlet is a member of. DatabaseServer. This is a optioal parameter that does ot actually require that a iput value be provided for it. If this parameter is used, the cmdlet uses the SQL Server istace ame to target the cofiguratio database specified via the DatabaseName parameter, which should be hosted i that database istace. If o value is supplied for this parameter, the cmdlet defaults to selectig the database istace hostig the cofiguratio database for the farm that the SharePoit 2010 server hostig the cmdlet is a member of. Item. This parameter is ot required. By default, if o item is specified, the etire farm is backed up. If a Item iput parameter is provided to specify the SharePoit compoet to be backed up, it must be a valid item i the farm. If the item has spaces i its ame, you must eclose the etire item withi quotatio marks ( ). If the exact ame or path for the desired compoet is ot kow, you ca use the ShowTree switch to list the compoets available withi the farm. (See the followig list for more iformatio o the ShowTree switch.) This parameter allows the cmdlet to be used to protect Web applicatios, service applicatios, cotet databases, ad much more withi your SharePoit farm. ShowTree. This is a optioal parameter. If the ShowTree parameter is icluded with the call of Backup-SPFarm for a backup, the cmdlet does ot complete a backup of SharePoit compoets. Istead, it displays the compoets i the farm so that their ames ca be used to request a backup. If a value is specified via the Item parameter, ay compoets that are ot childre of that iput are excluded ad marked with a asterisk (*). Ay compoets that you caot back up are eclosed withi square brackets ([ ]). The sytax to use Backup-SPCofiguratioDatabase i a script is really ot that differet from what you use with Backup-SPFarm. I fact, you may fid that i most scripted situatios, Backup-SPFarm with the CofiguratioOly parameter works well eough to keep you from itroducig aother cmdlet ito the script. Backup-SPCofiguratioDatabase works just fie i scripted scearios to protect your farm s cofiguratio data, but its primary use case is really more of a oe-off, ad hoc type of situatio i which you execute it whe a specific eed ad situatio arises. Backup-SPSite With the larger, farm-wide aspects of backig up SharePoit via PowerShell out of the way, let s look at the more graular backup operatios you ca perform with SharePoit 2010 s Power- Shell cmdlets. Well, operatios is a bit of a misomer there s really oly oe additioal cmdlet that we have t talked about for ograular backup activities with PowerShell i Share- Poit 2010: the Backup-SPSite cmdlet.

335 318 SharePoit 2010 Disaster Recovery Guide Before we dive ito the itty-gritty of that cmdlet, remember that the Backup-SPFarm cmdlet ca graularly protect a SharePoit eviromet. You ca use Backup-SPFarm s Item iput parameter to back up service applicatios, Web applicatios, cotet databases, search databases, ad other cotet compoets dow to the database level. If you eed to protect a item higher up i SharePoit 2010 s logical hierarchy, you re goig to eed to use Backup-SPFarm. But if you wat to completely back up idividual site collectios i a farm, your oly optio is Backup-SPSite, because the smallest item that Backup-SPFarm ca back up is a SharePoit cotet database. Keep the specifics of that distict level of graularity i mid whe preparig to use Backup- SPSite; you ca use it oly to create backups of SharePoit 2010 site collectios. You caot idividually target subsites (also kow as webs withi SharePoit 2010 s Object Model) beeath a site collectio with the cmdlet, or ca you target idividual items, lists, or libraries withi a site collectio or subsite. Admiistrators ca back up site collectios with the cmdlet by callig the Backup-SPSite cmdlet. I that call, they must specify at least two parameters: the Idetity parameter with a uiform resource locator (URL) or globally uique idetifier (GUID) of the target site collectio as a iput parameter, ad the Path parameter with the details of where to create ad store the backup file (either i the local file system of the server or a remote server via UNC path). Backup-SPSite -Idetity -Path \\backups\foo.bak Cautio: Aother limitatio of the Backup-SPSite cmdlet is that it ca oly complete full backups of a site collectio; ulike Backup-SPFarm, it caot execute differetial backups of a site collectio oce a full backup has bee made. This should affect oly the largest of site collectios, but keep it i mid whe cosiderig the tool. The Backup-SPSite cmdlet is also a great example of why the use of PowerShell to admiister SharePoit 2010 is such a importat developmet. PowerShell s core features, such as pipeliig, object orietatio, ad loopig, make it much, much easier to idividually back up multiple site collectios i a sigle process; somethig that would take quite a bit of VBScript ad calls with STSADM.exe i previous versios of SharePoit ca ow be accomplished i a sigle lie of PowerShell scriptig. For example, let s say that you eed to back up all the site collectios withi a Web applicatio owed by your compay s chief operatig officer (COO), a Mr. Joh Doe, o a much more frequet schedule tha the rest of your SharePoit farm, because Mr. Doe is kid of a big deal. A excerpt of the PowerShell script ecessary to do that should look somethig like this: $webapp = Get-SPWebApplicatio -idetity $sites = Get-SPSite $webapp -filter {$_.Ower = BAR\JDOE } Backup-SPSite -idetity $sites -path \\foo\backups

336 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 319 Now, you may otice that there s o loopig logic i the precedig script, ad there s a reaso for that. Every PowerShell cmdlet returs its results as a object, ad cmdlets that retur multiple objects actually retur those results as a array of objects. So the $sites variable is populated with all the site collectios that Mr. Doe ows, ot just oe. That array is the passed to Backup-SPSite, which iterates through each site collectio withi the array ad backs up each oe idividually. Aother great thig about PowerShell is that you ca cotiue to improve these three lies of script i a couple of ways. First, there s o eed to hardcode the URL of the targeted Web applicatio, the accout ID for Mr. Doe s accout, or the locatio of the backup files created by the process. Istead, you ca cofigure those items as parameters, which ca be passed ito a fuctio cotaiig the script, or as parameters for a etire script that the code would reside i. This allows you to reuse the script as eeded to cover multiple Web applicatios, users, ad storage locatios. The other thig you ca do is rewrite the script as show ext to reduce the umber of lies eeded to execute the desired backups: Get-SPWebApplicatio -idetity $URL Get-SPSite -filter {$_.Ower = $siteower} Backup- SPSite -path $backupstorage This versio of the script has doe away with the local variables ad is sedig the result of oe cmdlet directly to the ext oe listed i the lie. PowerShell uses a feature called pipeliig to ehace that trasfer process; it allows multiple cmdlets to be strug together, passig the output of oe cmdlet directly ito aother. The pipe characters ( ) betwee cmdlets i the precedig example represet the pipeliig activity. This is just oe example of some of the excitig ad useful thigs that admiistrators ca do with PowerShell thaks to its advaced features ad fuctioality. Because of that, it is importat to ot just zero i o what a sigle cmdlet like Backup-SPSite ca do, but to cosider how to combie with other SharePoit 2010 cmdlets like Get-SPWebApplicatio as well as other cmdlets, objects, applicatio programmig iterfaces (APIs), ad Web services that PowerShell makes available to you ad your scripts. But before you ca really get ito the creatio of those scripts, you eed to have a good uderstadig of what is eeded to effectively use this key cmdlet to properly back up a SharePoit 2010 site collectio. The list that follows details each switch that you ca use with Backup-SPSite ad its purpose: Idetity. Whe you back up a site collectio, this parameter is required ad must be a valid URL or GUID for the target site collectio. Path. Whe you back up a site collectio, this parameter is required ad must be a valid UNC or Widows directory path to a file that the backup is saved i. The accout logged ito the SharePoit 2010 Maagemet Shell must have permissio to write to the directory specified for this iput.

337 320 SharePoit 2010 Disaster Recovery Guide Tip: Although you must specify a file ame for the backup with this iput parameter, there is o required extesio to use whe specifyig the file ame for your backup. Use somethig easily idetifiable as a backup file, such as.bak. Regardless of the extesio you specify, SharePoit creates your backup at the selected path. AssigmetCollectio. This is a optioal parameter, iteded to allow for the proper disposal of objects. Carefully cosider usig this parameter if your call of Backup-SPSite also ivolves usig SharePoit s SPWeb, SPSite, or SPSiteAdmiistratio objects; otherwise, it is ot likely to be ecessary. Cofirm. This parameter is optioal. Whe used i a call of Backup-SPSite, it forces the cmdlet to prompt the user for cofirmatio prior to executig the backup. Force. This parameter is optioal; usig it forces Backup-SPSite to overwrite ay existig backup file matchig the value of the Idetity parameter should oe already exist. NoSiteLock. This parameter is optioal; its use keeps Backup-SPSite from lockig a site durig the executio of the site collectio backup. If this parameter is ot used, the target site collectio is oly available for users to read cotet from. They are ot able to add, modify, or delete cotet i it util the backup is doe ad the site is ulocked. If you expect your users to write to a target site collectio while it is beig backed up, do ot use this parameter uless you absolutely have to. Allowig write access to a SharePoit site while it is beig backed up ca lead to icosistecies or corruptio i your site s cotet. Keepig the target site collectio locked durig the backup process esures the highest-quality backup ad provides the best possible log-term experiece for your users. UseSqlSapshot. This parameter is optioal. Whe you use it, Backup-SPSite creates a SQL Server database sapshot of the cotet database cotaiig the site collectio, ad the backup of the site collectio is created by referecig the sapshot rather tha the database. Oce the backup is completed, the cmdlet deletes the database sapshot. This parameter ca be used oly if your SQL Server istace supports the creatio of database sapshots, so it is importat to review your SQL Server editio prior to usig it. If your istace does support sapshots, this parameter is recommeded because it makes your site collectio fully available to users durig the backup. Because the cmdlet is readig from the sapshot ad ot the database, there is a drastically reduced chace of resource cotetio betwee it ad the activities of your users. WhatIf. This is a optioal parameter. If this parameter is used, PowerShell displays a message statig what the outcome of ruig the cmdlet will be, but the cmdlet itself is ot executed. This ca be helpful whe testig scripts, allowig you to verify that you ca provide the correct set of iputs ad parameters to the cmdlet.

338 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 321 Usig SharePoit 2010 s Catastrophic Restore Cmdlets Restorig a backup created with SharePoit 2010 s backup cmdlets is completed i much the same maer as the process you followed to create the backup i the first place. The restore cmdlets use may of the same switches ad parameters that the backup cmdlets do, with some distictios. There are some distict permissios required to restore SharePoit backups: the service accout for the farm s SQL Server istace, the farm s Timer service accout, ad the idetity of the farm s Cetral Admiistratio site s applicatio pool must have read access to the storage locatio for your backup files. But the mai differece is that ow the ames of these cmdlets start with Restore as their verb istead of Backup. As with SharePoit 2010 s backup cmdlets, there are two restore cmdlets: Restore-SPFarm ad Restore-SPSite. Tip: You ca oly restore a SharePoit 2010 backup ito a farm patched to the same or more recet versio as the farm that the backup was made i. SharePoit 2010 s restore cmdlets do ot allow you to restore a backup to a farm with a older versio tha the farm that the backup origiated from. You also caot restore a backup created with a previous release of SharePoit, such as SharePoit 2007, ito a SharePoit 2010 farm. Restore-SPFarm The Restore-SPFarm cmdlet is the yag to Backup-SPFarm s yi, the white to its black, the 1 to its 0. You get the idea, right? Backup-SPFarm makes the backups, ad Restore-SPFarm restores them. Neat, huh? Now, there is oe other iterestig thig about Restore-SPFarm worth otig: there is o Restore-SPCofiguratioDatabase, so if you ve made a cofiguratio backup with Backup-SPCofiguratioDatabase, you eed to restore it with Restore-SPFarm just like you would a SharePoit 2010 backup that icludes both cotet ad cofiguratio data. Whether you re restorig cotet or cofiguratio data, the optios for Restore-SPFarm are the same; you ll fid that you ca use its two parameter sets for either situatio. Followig is a example of Restore-SPFarm i actio to perform a restore of the most recet backup file i the target directory: Restore-SPFarm -Directory \\foo\backups\ -RestoreMethod New Note: You ca also use Restore-SPFarm to restore catastrophic backups that were created through the Cetral Admiistratio site. The list that follows outlies the details of the first parameter set for Restore-SPFarm, which actually restores a backup file. Directory. Whe you re performig a restore with Restore-SPFarm, this parameter is required (uless the ShowTree parameter is provided; see the ext list for further

339 322 SharePoit 2010 Disaster Recovery Guide iformatio). This parameter idicates the locatio of the backup to be restored. The target directory ca be o the file system if SharePoit is istalled o the same server as its back-ed database; otherwise, it must be a UNC shared directory. This directory ca store multiple backups for your farm. The most recet backup is used uless a BackupID parameter is also provided. RestoreMethod. Whe you re performig a restore with Restore-SPFarm, this parameter is required (uless the ShowTree parameter is provided). Acceptable iput parameter values are New or Overwrite, ad they determie whether you are restorig the backup to a differet farm (the New optio) or to the curret farm (the Overwrite optio). You should use the Overwrite optio whe you are restorig the backup to the same farm that the backup was created with; if you are restorig the backup to a differet farm, use the New optio. NewDatabaseServer. This iput parameter is ot required ad ca be used oly with the RestoreMethod parameter. Whe used, it is set as the default database istace for the restored farm. AssigmetCollectio. This is a optioal parameter, iteded to allow for the proper disposal of objects. Carefully cosider usig this parameter if your call of Restore-SPFarm also ivolves usig SharePoit s SPWeb, SPSite, or SPSiteAdmiistratio objects; otherwise, it is ot likely to be ecessary. RestoreThreads. This parameter, which must be a iteger from 1 to 10, is ot required. It determies the umber of threads SharePoit uses to complete the restore operatio. If o RestoreThreads value is provided, SharePoit defaults to three threads. Note: You eed to take the same cosideratios for performace ad resources metioed for the BackupThreads parameter i the Backup-SPFarm cmdlet ito accout with the RestoreThreads parameter of Restore-SPFarm. CofiguratioOly. This is a optioal parameter that does ot actually require a iput value to be provided for it. If you use this switch, the cmdlet oly restores the cofiguratio data for the item targeted, whether that is the full farm or a idividual compoet of that farm. If you are restorig a backup created with the Backup-SPCofiguratioDatabase cmdlet, you must use this switch to properly restore the cofiguratio backup. Remember: restorig a farm s cofiguratio data does ot iclude its service applicatios or Web applicatios. You must re-create these items or restore them via cotet backups after the cofiguratio backup is complete to retur them to your farm. Cofirm. This is a optioal parameter. If this parameter is used with a iput value of True, the cmdlet prompts the user to cofirm that he wats to proceed with the actio. If a

340 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 323 value of False is provided, the cmdlet proceeds without promptig for permissio oce executed. The default value for this parameter is False. Force. This is a optioal parameter that does ot actually require a iput value to be provided for it. If this switch is ot used, the cmdlet does ot proceed with the restore operatio if it is goig to overwrite a existig SharePoit 2010 farm. If it is used, that check is overridde, ad the restore is executed o matter what. Item. This parameter is ot required. By default, if o item is specified, the etire farm is restored. If a Item iput parameter is provided to specify the SharePoit compoet to be restored, it must be a valid item i the farm. If the item has spaces i its ame, the etire item must be eclosed withi quotatio marks ( ). If the exact ame or path for the desired compoet is ukow, you ca use the ShowTree switch to list the compoets available withi the farm. Tip: If you are usig the Item parameter to restore a farm s Secure Store Service, you must refresh the store s passphrase with the Update-SPSecureStoreApplicatioServerKey cmdlet after you have successfully restored it. Percetage. This iput parameter is ot required. If a value is specified for the Percetage iput parameter, it must be a iteger betwee 1 ad 100 ad is used to determie the frequecy with which Restore-SPFarm reports progress of the restore operatio. For example, specifyig a value of 20 displays the progress of the restore operatio for every 20 percet of the operatio that is completed. If o Percetage parameter is specified, STSADM.exe defaults to reportig progress every 5 percet of the operatio. This iput parameter has o affect o the outcome of the restore operatio; it oly affects the amout of iformatio that the cmdlet reports about its activities durig the operatio. SharePoit is ot able to calculate the completed percet of the restore operatio with 100 percet accuracy. You may fid that your actual progress updates do ot appear with exactly the requested frequecy. Tip: For large SharePoit compoets, Microsoft recommeds that a Percetage iput of 1 be used to provide the best status data about your restore operatio. BackupID. This iput parameter is ot required. If you use it, it must be a valid GUID for a backup package i the storage directory idicated by the Directory parameter. You ca fid the GUIDs for the backup packages i the target directory via the Get-SPBackupHistory cmdlet, discussed later i this chapter. If o BackupID parameter is used, the cmdlet selects the most recet backup i the target directory. FarmCredetials. This iput parameter is ot required. If you use it, this parameter idicates the credetials that the farm employs oce it is restored, such as applicatio pools for

341 324 SharePoit 2010 Disaster Recovery Guide restored SharePoit Web applicatios. If a Web applicatio s applicatio pool already exists, this data is igored, ad the farm uses the existig credetials. WhatIf. This is a optioal parameter. If this parameter is used, PowerShell displays a message statig what the outcome of ruig the cmdlet will be, but the cmdlet itself is ot executed. This ca be helpful whe testig scripts, allowig you to verify that you ca provide the correct set of iputs ad parameters to the cmdlet. The secod parameter set for Restore-SPFarm is best used to obtai valuable iformatio about your farm for restorig it, rather tha a actual restore operatio. The key parameter i this set is the ShowTree parameter; its presece idicates that the secod parameter set is beig used istead of the first. Directory. Whe you re performig a restore with Restore-SPFarm, this parameter is required (uless the ShowTree parameter is provided; see the ext bullet for further iformatio). This parameter idicates the locatio of the backup to be restored. The target directory ca be o the file system if SharePoit is istalled o the same server as its back-ed database; otherwise, it must be a UNC shared directory. This directory ca store multiple backups for your farm, the most recet backup is used uless a BackupID parameter is also provided. ShowTree. This is a optioal parameter. If the ShowTree parameter is icluded with the call of Restore-SPFarm for a restore, the cmdlet does ot complete a restore of ay SharePoit compoets. Istead, it displays the compoets i the target backup package so that you ca use their ames to request a restore. If a value is specified via the Item parameter, ay compoets that are ot childre of that iput are excluded ad marked with a asterisk (*). Ay compoets that caot be restored are eclosed withi square brackets ([<item that ca t be restored4]). AssigmetCollectio. This is a optioal parameter. It is used with this parameter set i the same way that it is i the first parameter set. CofiguratioOly. This is a optioal parameter. It is used with this parameter set i the same way that it is i the first parameter set. Item. This is a optioal parameter. It is used with this parameter set i the same way that it is i the first parameter set. WhatIf. This is a optioal parameter. It is used with this parameter set i the same way that it is i the first parameter set. Restore-SPSite If you thik of the Restore-SPFarm cmdlet as peaut butter is to the Backup-SPFarm cmdlet s jelly, the Restore-SPSite cmdlet is the baco to the Backup-SPSite cmdlet s eggs two great

342 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 325 tastes that are great together. Whe you eed to restore a site collectio backup created with Backup-SPSite, you re goig to use Restore-SPSite. Makes sese, right? I fact, Restore- SPSite is the oly way to restore a site collectio backup created with SharePoit s out-ofthe-box tools; you ca t restore that backup through the Cetral Admiistratio site or with SQL Server s maagemet tools. Here s a quick example of Restore-SPSite i actio: Restore-SPSite Idetity -Path \\foo\backups\bar.bak The list that follows outlies each parameter available to be used with the Restore-SPFarm cmdlet ad the possible optios you ca use for each parameter: Idetity. Whe you re restorig a site collectio backup, this parameter is required ad is the URL that you wat users to eter whe accessig your restored site collectio. You ca restore Backup-SPSite s site collectio backups to a ew URL ad attempt to update all the paths withi the backup package to reflect the ew URL for the site collectio, as log as SharePoit is able to create a site collectio at that path. Make sure to fully test the restored site collectio s resources that deped o this iformatio, such as liks, avigatio cotrols, ad search results, to cofirm that all the collectio s data was correctly updated to the ew path. You ca also use a URL for a existig site collectio, which completely overwrites the existig site collectio, but you must use the Force parameter to eable this actio. Path. Whe you re restorig a site collectio, this parameter is required ad must be a valid UNC or Widows file path to a backup package created via Backup-SPFarm. AssigmetCollectio. This is a optioal parameter, iteded to allow for the proper disposal of objects. Carefully cosider usig this parameter if your call of Restore-SPSite also ivolves usig SharePoit s SPWeb, SPSite, or SPSiteAdmiistratio objects; otherwise, it is ot likely to be ecessary. HostHeaderWebApplicatioURL. Whe you re restorig a site collectio backup, this parameter is ot required. You use it if you wat to restore your site collectio to a Web applicatio with a differet URL tha the value specified for the URL iput parameter. This parameter is explaied i more detail later. Cofirm. This is a optioal parameter. If it is used with a iput value of True, the cmdlet prompts the user to cofirm that he wats to proceed with the actio. If a value of False is provided, the cmdlet proceeds without promptig for permissio oce executed. The default value for this parameter is False. CotetDatabase. This is a optioal parameter. If this parameter is used, the site collectio is provisioed withi the cotet database matchig the value provided. If the parameter is ot used, the site collectio is automatically placed i the cotet database with the least umber of site collectios i it ad a status of Ready.

343 326 SharePoit 2010 Disaster Recovery Guide Force. Whe you re restorig a site collectio backup, this switch is ot required. Usig it istructs Restore-SPSite to overwrite ay existig site collectio matchig the value of the URL parameter. GradualDelete. This optioal parameter alters the mechaics of the restore operatio whe you also employ the Force parameter. Whe you execute a site collectio restore that overwrites a existig site collectio, two sets of operatios take place at the database level. The first set of operatios etails the deletio of all existig items withi the target cotet database that are tied to the site collectio beig overwritte. Oce the existig site collectio data is deleted, the secod set of operatios that take place ivolve the actual restoratio of the site collectio ad the isertio of ew rows ito the cotet database. Without the use of the GradualDelete parameter, the delete ad isert operatios execute i serial fashio. Because the deletio of existig cotet throughout the cotet database ca take a sigificat amout of time, poor performace o restore may result. Whe you employ the GradualDelete parameter, however, the deletio of existig site collectio data from the cotet database is effectively deferred util after the restore operatio has take place. Deferred deletios are hadled by a Gradual Site Delete timer job that is established ad defaults to ruig daily for each Web applicatio i the farm. Deferrig deletio of site collectio cotet ca result i sigificat performace icreases, particularly whe a substatial amout of existig site collectio cotet resides i the cotet database. Usig this parameter whe overwritig a existig site collectio ca reduce the performace impact of the operatio o the SharePoit servers i your farm, as well as o SQL Server. Microsoft recommeds usig this parameter whe restorig large site collectios; we recommed that you test this parameter wheever possible to assess its impact ad implicatios o the usability of a target site collectio before usig it i a productio eviromet. WhatIf. This is a optioal parameter. It is used with this parameter set i the same way as it is i the first parameter set. You ca use the HostHeaderWebApplicatioURL parameter to restore a site collectio to a URL differet from the URL of its paret Web applicatio. If you pass a value of for the HostHeaderWebApplicatioURL parameter as a additio to the previous example, the restore operatio creates a site collectio for the foo address uder the bar Web applicatio eve though they have differet URLs. Whe it rus the restore operatio, Restore-SPSite geerates a host header for the target Web applicatio i IIS so that requests submitted to the server for are mapped to the restored site collectio eve though it is withi a Web applicatio with a differet URL ( SharePoit site collectios created usig a host header i this fashio are called host-amed site collectios. Ulike ormal site collectios, host-amed site collectios use IIS host headers to direct traffic to the correct site collectio istead of maaged paths. This allows multiple site collectios withi a sigle Web applicatio to have a uique URL that ca be used to access its

344 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 327 cotet idepedet of the other site collectios i the Web applicatio. Keep i mid that there are some drawbacks to host-amed site collectios; they are ot compatible with alterate access mappigs (AAMs) or the use of ay zoe other tha the Default zoe, so each site collectio ca oly respod to traffic o a sigle URL. For more iformatio o host-amed site collectios ad their impact o the architecture ad admiistratio of your SharePoit farm, review this article from the Microsoft Kowledge Base: cc aspx. Restore-SPSite also has a secod parameter set available for use, although it icludes most of the same parameters ad optios as the first set. This secod set allows for more cotrol over what SharePoit cotet database the site collectio is stored i whe the cmdlet restores it. The oly parameter from the first set ot used by the secod set is CotetDatabase. It is replaced by the two parameters listed ext. (All the other parameters from the precedig list above ca be used i cojuctio with these two parameters as desired.) DatabaseName. This is a optioal parameter. If you use this parameter, the site collectio is provisioed withi the cotet database matchig the value provided, as log as it is a valid database ame. If the parameter is ot used, the site collectio is automatically placed i the cotet database with the lowest umber of site collectios ad a status of Ready. DatabaseServer. This is a optioal parameter. It is used to specify the SQL Server istace that cotais the database provided by the DatabaseName parameter. The value provided for this parameter must be a valid SQL Server istace that the farm ca access. Furthermore, a valid value must be provided for the DatabaseName parameter for the cmdlet to successfully use this parameter. Reviewig Your Backup ad Restore History The purpose of the Get-SPBackupHistory cmdlet is pretty self-explaatory. It outputs a listig of the Backup-SPFarm ad Restore-SPFarm operatios that have bee coducted usig the files i the specified directory. The Get-SPBackupHistory cmdlet uses the spbrtoc.xml file stored withi the target backup storage directory to determie ad display iformatio. Cautio: The Get-SPBackupHistory cmdlet ca oly be used to display iformatio o backups created via the Backup-SPFarm cmdlet, restores coducted via the Restore- SPFarm cmdlet, or catastrophic operatios ru usig the Cetral Admiistratio site s backup or restore tools. It does ot work for other types of backups, such as site collectio backups via Backup-SPSite. A sample Get-SPBackupHistory request is listed ext: Get-SPBackupHistory -Directory \\backups

345 328 SharePoit 2010 Disaster Recovery Guide You ca use the followig switches ad iput parameters with the Get-SPBackupHistory operatio: Directory. This iput parameter is required whe ruig Get-SPBackupHistory. The same rules apply to this parameter as the Directory iput parameters for the restore ad backup cmdlets discussed earlier. AssigmetCollectio. This is a optioal parameter, iteded to allow for the proper disposal of objects. Cosider usig this parameter if your call of Get-SPBackupHistory also ivolves usig SharePoit s SPWeb, SPSite, or SPSiteAdmiistratio objects; otherwise, it is ot likely to be ecessary. ShowBackup. This iput switch is ot required whe ruig Get-SPBackupHistory. Whe used, it filters the output of the operatio so that the cmdlet returs oly backup operatio history data. ShowRestore. This iput switch is ot required whe ruig Get-SPBackupHistory. Whe used, it filters the output of the operatio so that the cmdlet displays oly restore operatio history data. Note: If you omit the Backup ad Restore switches from the Get-SPBackupHistory request, the cmdlet returs the history data for all backup ad restore operatios. If you use the Backup ad Restore switches with the Get-SPBackupHistory request, the cmdlet returs the history data for all backup ad restore operatios. Now that you have successfully ru the Get-SPBackupHistory cmdlet, let s talk about its output ad what you ca do with it. A review of its output demostrates why PowerShell makes commad lie admiistratio i SharePoit 2010 so much better. Because Get-SPBackupHistory returs a array of all backup ad restore operatios ru i the target directory, it provides much more useful ad maageable data tha what was available with similar commads i previous versios of SharePoit. This meas you do t have to trasform the cmdlet s output ito a useable format first if you wat to extract pertiet data from it with a scripted process; it s already i such a format. Ad thaks to PowerShell s pipeliig capabilities, you ca do thigs like pass its output right ito a query to select the most recet successful backup, ad the pass the BackupID for that istace directly to Restore-SPFarm. The result: i oe lie of PowerShell script, you ca use Get- SPBackupHistory to automatically restore your most recet backup. Documetig Your Cofiguratio As hard as it may be to cosider such a possibility (especially with the ew fuctioality that has bee added to SharePoit 2010 that we ve bee talkig about for the past several pages), there is still a chace that you may ot be able to completely ad successfully restore your SharePoit 2010

346 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 329 farm to its origial state before disaster struck. You could have a backup that failed the ight before, a backup set that has become corrupted, or backup files that were deleted or lost altogether. Regardless of what may cause such a situatio, it is a good idea to have a idea of how you eed to go about recostructig your SharePoit 2010 eviromet if you do t have the luxury of restorig its cotet ad cofiguratio from backups. Not to metio, there are items i your SharePoit 2010 farm, such as its service applicatios, that you may ot be able to back up ad therefore caot restore from a backup file. But the problem is that i most IT systems, the oly costat i the eviromet is chage. Because your farm s cofiguratio ad setup ca be costatly chagig ad is ofte beig modified by more tha oe user at oce, it becomes importat to have a effective chage cotrol process i place for your orgaizatio to better track, maage, ad approve chages to your farm. Not to metio the huma factor: it ca be all too easy for a admiistrator to put off documetatio or omit key data i documetatio. That s uderstadable; the level of detail that these fuctios require to properly execute ca be dautig at best ad isurmoutable at worst. The questio becomes this: what do you do to capture that cofiguratio data? We ve already covered tools like Backup-SPFarm with the CofiguratioOly parameter ad SQL Server backups of your cofiguratio database combied with Backup-SPCofiguratioDatabase. Ad do t forget to cosider other optios for preservig your SharePoit farm s cofiguratio iformatio, like queryig the Widows Evet logs, IIS logs, SharePoit logs, ad scriptig queries agaist Widows Maagemet Istrumetatio (WMI) objects withi your farm s servers. Microsoft also has cofiguratio maagemet tools i the System Ceter suite, such as Cofiguratio Maager ad Service Maager, that you ca use to cotrol ad track chages you make i your farm. Aother oe of those thigs we love about PowerShell is that its 2.0 versio also offers a cmdlet desiged to help you mitigate the risk of chage, which offers a additioal approach for recordig details about how your farm is cofigured: Export-Clixml. Export-Clixml coverts ay objects (such as PowerShell objects) ito XML ad stores that XML data i a file. The cmdlet also provides several optios for use, such as the ability to idetify how deeply ito the object the coversio process should go. (The default is two; decidig how may levels of data from withi aother object ca be time-cosumig.) The ability of the Export-Clixml cmdlet to trasform objects ito XML documets meas that you ca take the output of ay SharePoit 2010 cmdlet ad covert it ito a static text documet that lists the curret state ad cofiguratio of may importat facets of your SharePoit 2010 farm. For example, you ca pipe the results of Get-SPWebApplicatio to Export-Clixml to create a complete list of your farm s Web applicatios, or you ca covert the output of Get- SPFarm ad Get-SPFarmCofig to obtai detailed data about your etire SharePoit 2010 farm ad its cofiguratio.

347 330 SharePoit 2010 Disaster Recovery Guide The major drawback to this solutio is that it is all documetatio; you caot restore its output to aother SharePoit 2010 farm i the evet of a disaster. Istead, you must use the data created by these cmdlets as a poit of referece, with the itetio of maually re-creatig your farm s setup ad cofiguratio i a ew SharePoit 2010 farm. Keep i mid, though, that ay effort you make to gather more poit-i-time data about the cofiguratio ad setup of your farm ca greatly improve your ability to ot just get SharePoit back up ad ruig after a disaster but retur it to a state as close to its coditio prior to the disaster as possible. For more iformatio o Export-Clixml ad a effective example of how to use it i a script to completely documet the cofiguratio of your farm, take a look at e-us/library/ff aspx. Graular Backup ad Restore via PowerShell I Chapter 9, we itroduced the cocept of graular backup ad restore: export ad import fuctioality that you ca use to protect idividual subsites (also kow as webs i the Share- Poit object model) ad lists (such as documet libraries, form libraries, aoucemets lists, or custom lists) through the SharePoit Cetral Admiistratio site. Similar fuctioality is also available through the SharePoit 2010 Maagemet Cosole s PowerShell cmdlets, allowig those items to be protected via scripted or maual use of those cmdlets. Keep i mid that, like the Cetral Admiistratio site s graular backup ad restore tools, these cmdlets do ot protect their targeted SharePoit compoets as completely as the backup ad restore cmdlets we have discussed i this chapter. The iformatio we ve already provided i Chapter 9 covers these differeces icely ad goes ito excellet detail about the uses of ad purposes for these cmdlets. We recommed reviewig that chapter if you eed a refresher o the matter. The followig sectios cotai specific iformatio ad istructios for usig each of these export ad import cmdlets. Export-SPWeb The Export-SPWeb cmdlet exports the cotets of a web or list withi a web to oe or more files, as show i the example that follows: Export-SPWeb Idetity -Path c:\backups\site1.cmp If you wat to script a call of Export-SPWeb, especially if you wat to protect multiple webs at oce, the approach you ll be most likely to take is goig to be similar to what we ve outlied previously i the sectio o Backup-SPSite. The differece is that you re ot quite doe oce you ve arrived at oe or more target site collectios; you still eed to select the desired webs withi those site collectios with the Get-SPWeb cmdlet. Oce you ve selected the correct webs with Get-SPWeb, you ca pass that array of webs to Export-SPWeb for a graular backup. Followig is a example of how to accomplish this: Get-SPWebApplicatio -idetity $URL Get-SPSite -filter {$_.Ower = $siteower} Get- SPWeb Export-SPWeb -path $backupstorage

348 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 331 The items i the list that follow describe the various parameters that ca be used to call Export- SPWeb to export or create a graular backup of a SharePoit site, oe or all of its subsites, or a list withi a site: Idetity. Whe you export a web or a list withi a web, this parameter is required ad must be a valid URL or GUID for the target item. Path. Whe you export a web or a list withi a web, this parameter is required ad must be a valid UNC or Widows directory path to a file that the backup is saved i. The accout logged ito the SharePoit 2010 Maagemet Shell must have permissio to write to the directory specified for this iput. AssigmetCollectio. This is a optioal parameter, iteded to allow for the proper disposal of objects. Carefully cosider usig this parameter if your call of Export-SPWeb also ivolves usig SharePoit s SPWeb, SPSite, or SPSiteAdmiistratio objects; otherwise, it is ot likely to be ecessary. CompressioSize. This parameter is ot required. If used, it idicates the maximum size that the compressed export files are allowed to be created to ad allows you to set a preferred target size for the CAB files (typically saved as files with a.cmp extesio) created by the operatio. If the total size of the export is greater tha that amout, it is automatically broke ito multiple files. Cofirm. This is a optioal parameter. If this parameter is used with a iput value of True, the cmdlet prompts the user to cofirm that he wats to proceed with the actio. If a value of False is provided, the cmdlet proceeds without promptig for permissio oce executed. The default value for this parameter is False. Force. This is a optioal parameter that does ot actually require a iput value to be provided for it. If this switch is ot used, the cmdlet does ot proceed with the backup operatio if it estimates that there is ot eough disk space available to store the backup. If it is used, that check is overridde, ad the backup is executed regardless of how much storage is available. Item. This parameter is ot required. It sets the URL of the Web applicatio, GUID, or object to be exported ad must be a valid SharePoit URL withi the farm. Whe usig this parameter, the full address of the target item is ot required. For example, if you are targetig the subsite bar withi the site collectio, you would provide /bar for this parameter. Targetig the Caledar list withi that bar subsite would be /bar/lists/caledar. Of course, you could also use the GUID for each of these items to specify them. HaltOError. This iput parameter is ot required; if it is icluded, the export process is stopped ad ot completed if errors are ecoutered. HaltOWarig. This iput parameter is ot required; if it is icluded, the export process is stopped ad ot completed if warigs are ecoutered.

349 332 SharePoit 2010 Disaster Recovery Guide IcludeUserSecurity. This iput parameter is ot required; if it is icluded, the export process icludes the user security settigs of the targeted item i the export files. IcludeVersios. This iput parameter is ot required; if it is icluded, the export process icludes the versioig data of the targeted item i the export files based o the type of file or list item history provided as a parameter. If o value is provided for this parameter, a default value of 1 is used to export the target s last major versio, which ca also be targeted with a value of LastMajor. You ca use this parameter to target the most curret versio (major or mior) usig a value of CurretVersio or 2, both the last major ad mior versios for the item with a value of LastMajoradMior or 3, or all versios for the targeted item with a value of All or 4. NoFileCompressio. This iput parameter is ot required; if it is icluded, the export process does ot compress the export files it creates. Usig this parameter does create a simple problem if you do ot direct the export to its ow directory. Because the files are ot compressed, they are ot cotaied i a CAB file. For performace reasos, Microsoft recommeds compressig the export files; their research shows that compressio reduces the completio time for export processes by up to 30 percet. If this parameter is used durig a export operatio, it must also be used durig a import operatio usig the export files it creates. NoLogFile. This iput parameter is ot required; if it is icluded, the export process does ot create a log file for the export process. It should oly be used to improve performace of the export process i extreme coditios; i most circumstaces, a log file is desired for export operatios. UseSQLSapshot. This iput parameter is ot required; whe you use it, Export-SPWeb creates a SQL Server database sapshot of the cotet database cotaiig the targeted item. The export is created by referecig the sapshot rather tha the database. Oce the export is completed, the cmdlet deletes the database sapshot. You ca oly use this parameter if your SQL Server istace supports the creatio of database sapshots. That s why it is importat to review your SQL Server editio prior to usig it. If your istace does support sapshots, this parameter is recommeded because, ulike Backup-SPSite, the targeted site collectio is ot automatically locked durig the operatio. Uless you maually take actio to set the target to read oly, your users ca modify it durig the export process. Because the cmdlet is readig from the sapshot ad ot the database, there is a drastically reduced chace of resource cotetio betwee it ad the activities of your users. WhatIf. This is a optioal parameter. If you use this parameter, PowerShell displays a message statig what the outcome of ruig the cmdlet will be, but the cmdlet itself is ot executed. This ca be helpful whe testig scripts, allowig you to verify that you ca provide the correct set of iputs ad parameters to the cmdlet.

350 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 333 Tip: There are several other SharePoit 2010 cmdlets desiged to export data out of a specific area of aspect of a farm that you may wat to evaluate ad test for use withi your farm. May of these cmdlets are iteded to protect specific service applicatios or fuctioality that is available oly i SharePoit Server 2010, which ca limit their scope ad usefuless depedig o what versio of SharePoit 2010 you re usig ad what you ve chose to implemet ad eable withi your farm. These cmdlets iclude, but are ot limited to, Export- SPBusiessDataCatalogModel, Export-SPBusiessDataCatalogPartitioData, Export-SPEterpriseSearchTopology, Export-SPIfoPathAdmiistratio- Files, Export-SPMetadataWebServicePartitioData, Export-SPProfileService- ApplicatioTeat, adexport-spsitesubscriptiosettigs. Import-SPWeb Import-SPWeb is the flip side of the Export-SPWeb s coi; it imports the cotets of exports created with Export-SPWeb back ito a SharePoit 2010 eviromet. The example that follows shows a import operatio that imports both the cotet ad the versio data cotaied i the export file ad overwrites ay SharePoit cotet already existig i the target locatio: Import-SPWeb Idetity -Path c:\backups\site1.cmp UpdateVersios -Overwrite The items i the followig list describe the various parameters that ca be used to call Import- SPWeb to import or restore a graular backup of a SharePoit subsite or list: Idetity. Whe you import a web or a list withi a web, this parameter is required ad must be a valid URL or GUID for the target item that the export is imported ito. Path. Whe you import a web or a list withi a web, this parameter is required ad must be a valid UNC or Widows directory path to the file or files to be imported. The accout logged ito the SharePoit 2010 Maagemet Shell must have permissio to read to the directory specified for this iput. AssigmetCollectio. This is a optioal parameter, iteded to allow for the proper disposal of objects. Carefully cosider usig this parameter if your call of Import-SPWeb also ivolves usig SharePoit s SPWeb, SPSite, or SPSiteAdmiistratio objects; otherwise, it is ot likely to be ecessary. ActivateSolutios. This parameter is ot required. If used, it idicates that ay user solutios should be activated as part of the import process.

351 334 SharePoit 2010 Disaster Recovery Guide Cofirm. This is a optioal parameter. If this parameter is used with a iput value of True, the cmdlet prompts the user to cofirm that he wats to proceed with the actio. If a value of False is provided, the cmdlet proceeds without promptig for permissio oce executed. The default value for this parameter is False. Force. This is a optioal parameter that does ot actually require a iput value to be provided for it. Usig it istructs Import-SPWeb to overwrite ay existig item matchig the value of the Idetity parameter. HaltOError. This iput parameter is ot required; if it is icluded, the import process is stopped ad ot completed if errors are ecoutered. HaltOWarig. This iput parameter is ot required; if it is icluded, the import process is stopped ad ot completed if warigs are ecoutered. IcludeUserCustomActio. This iput parameter is ot required; if it is icluded, the import process icludes the user custom actios of the targeted item i the import files. IcludeUserSecurity. This iput parameter is ot required; if it is icluded, the import process icludes the user security settigs of the targeted item i the import files. UpdateVersios. This iput parameter is ot required; if it is icluded, the import process uses it to determie how versio data i the imported file is itegrated ito existig versios i the target item. If o value is provided for this parameter, a default value of 1 is used to import the versio data as a ew versio, which ca also be accomplished with a value of Apped. You ca also use this parameter to overwrite the target item with a value of Overwrite ad all its existig versios with the ewly imported item, or you ca igore ay existig files i the targeted locatio with a value of Igore. NoFileCompressio. This iput parameter is ot required; if it is icluded, the import process does ot compress the import files it creates. For performace reasos, Microsoft recommeds compressig the import files. Their research shows that it reduces the completio time for import processes by up to 30 percet. If you use this parameter durig a export operatio, you must also use it durig ay import operatio usig the export files it creates. NoLogFile. This iput parameter is ot required; if it is icluded, the import process does ot create a log file for the import process. It should oly be used to improve performace of the import process i extreme coditios; i most circumstaces, a log file is desired for import operatios. WhatIf. This is a optioal parameter. If you use this parameter, PowerShell displays a message statig what the outcome of ruig the cmdlet will be, but the cmdlet is ot executed. This ca be helpful whe testig scripts, allowig you to verify that you ca provide the correct set of iputs ad parameters to the cmdlet.

352 Chapter 10 SharePoit 2010 Commad Lie Backup ad Restore: PowerShell 335 Tip: Just like Export-SPWeb, there are several other SharePoit 2010 cmdlets that ca import previously exported data ito a specific area of aspect of a farm that you may wat to evaluate ad test for use withi your farm. These cmdlets iclude, but are ot limited to, Import- SPBusiessDataCatalogModel, Import-SPBusiessDataCatalogPartitioData, Import-SPEterpriseSearchTopology, Import-SPIfoPathAdmiistratioFiles, Import-SPMetadataWebServicePartitioData, Import-SPProfileServiceApplicatioTeat, adimport-spsitesubscriptiosettigs. Coclusio SharePoit 2010 s backup ad restore PowerShell cmdlets are versatile tools. They ca cover your etire farm dow to uits as small as the cotets of a list ad most of the cofiguratio data for that list, ad they ca tailor your requests to meet your specific requiremets. If you are a admiistrator who prefers usig the commad lie ad scriptig to maage SharePoit over graphical tools, these cmdlets should certaily appeal to you. But they are ot the oly tools you eed to preserve ad recover from your SharePoit eviromet i the case of a disaster. O its ow, SharePoit 2010 s backup ad restore cmdlets, like the Cetral Admiistratio site backup ad restore tools, provide you the most beefits whe used before you modify your SharePoit eviromet. The tool allows you to submit just a sigle admiistrative operatio at a time ad rus it immediately, so you have to kow whe you are goig to eed it before you ru it, ad you caot schedule a backup or restore to ru i the future. By itself, PowerShell does ot provide optios to schedule a regularly repeated operatio, such as a ightly ru of the backup operatio, but that does ot mea such a activity is ot possible. Because PowerShell is a commad lie shell, you ca create a Widows scheduled task o your server that submits a request to ru a scripted PowerShell backup operatio o a defied regular basis, allowig you to icorporate programmig logic ad additioal operatios ito your request. SharePoit 2010 s backup ad restore cmdlets share some other commo drawbacks with the Cetral Admiistratio s tool. As previously metioed i this chapter, you caot completely back up compoets smaller tha a site collectio. The export ad import operatios allow you to migrate the cotets of subsites ad lists as eeded, but they do ot costitute a full-fledged backup optio. The backup ad restore cmdlets covered i this chapter do ot allow you to maage the backup files they create. Therefore, if you are ot careful about moitorig ad maagig the disk space that your storage locatio uses, you could ru out of room to store your crucial files or ed up retaiig backups that have goe stale ad are o loger relevat. Now that you have see SharePoit 2010 s PowerShell cmdlets related to backig up ad restorig your SharePoit eviromet, you should be able to aswer the followig questios about

353 336 SharePoit 2010 Disaster Recovery Guide their capabilities. You ca fid the aswers to these questios i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at 1. What are the two ways to back up a farm s cofiguratio data idepedet of its cotet? 2. What cmdlet should you use to back up the cofiguratio data of a farm that the server hostig the cmdlet is ot attached to, ad what parameters should you use to target that remote farm? 3. What aspects of a SharePoit 2010 farm are ot icluded i a cofiguratio-oly backup? 4. What SharePoit 2010 cmdlet ca you use to view the history of all backup ad restore operatios that have bee executed usig the files i a targeted directory? 5. What are the beefits of usig the UseSQLSapshot parameter for the Export-SPWeb cmdlet?

354 11 SharePoit 2010 Disaster Recovery Developmet I This Chapter Hey Admiistrator I m Talki to You! The SharePoit Object Model Volume Shadow Copy Service Rollig Your Ow Backup ad Restore Approach Desigig Applicatios for Disaster Recovery Readiess I a book that approaches SharePoit disaster recovery with a strog eye toward ifrastructure admiistratio ad operatios, it may seem surprisig to fid this chapter estled amog discussios o topics such as SQL Server high availability, SharePoit server farm architectures, ad the most appropriate backup mechaism to support a give disaster recovery strategy. Furthermore, may are of the opiio that custom developmet ad ifrastructure activities mix about as well as oil ad water. This book adopts a more holistic view. As far as Web-based platforms go, SharePoit is a behemoth. Much like the Roma Empire i 117 A.D., SharePoit reaches to all corers of the techological ladscape. To leverage Share- Poit to greatest effect, you must figuratively wear may hats ad have a multidiscipliary uderstadig of the platform. Cultivatig a healthy respect ad some degree of skill i a variety of disciplies such as etworkig, server maagemet, database techologies, ad custom developmet is essetial. Custom developmet is the primary focus of this chapter. Hey Admiistrator I m Talki to You! This probably does t surprise you, but we assume that you are more likely a admiistrator or a disaster recovery architect tha a developer. We expect some developers to pick up this book ad take a iterest i this chapter, but they are probably i the miority. Based o that rough demographic breakdow, you might be oe of the may thikig, Okay, so I m a SharePoit admiistrator. I m ot a developer. Why should I eve bother with this 337

355 338 SharePoit 2010 Disaster Recovery Guide chapter? If that s what you are thikig, the pull out a ruler, rap yourself across the kuckles, ad re-read Chapter 10, SharePoit 2010 Commad Lie Backup ad Restore: PowerShell. PowerShell is here, ad it is a game chager. With the proliferatio of PowerShell throughout SharePoit ad may of Microsoft s other server platforms, the oce clear lie of separatio betwee admiistrators ad developers has become exceptioally blurry. For most practical purposes, it ca eve be said that the lie is goe altogether. The Dark Days Before PowerShell Before PowerShell, there were a sigificat umber of admiistrative tasks that could oly be accomplished through custom code. May of the tasks were t particularly difficult or ivolved; they just could t be performed without the help of a developer. If STSADM.exe did t iclude support for the task to be accomplished, you were out of luck. SharePoit vetera admiistrators may remember the days of seekig a developer s help to write small cosole applicatios to make seemigly simple chages to site collectios, Web applicatios, the SharePoit farm, ad other aspects of their SharePoit eviromets. For example, SharePoit 2007 provided a mechaism (which is still preset i SharePoit 2010) that allowed a Web applicatio to retur a custom HTML page whe a user received a HTTP 404 error for requestig a page that could t be foud. Cofigurig a Web applicatio to use a custom 404 page was as straightforward as settig the FileNotFoudPage property o a target Web applicatio. Ufortuately, there was o simple way for a admiistrator to do this. I fact, Microsoft wrote a support article ( that described the creatio of a commad lie applicatio just to make the chage. The applicatio that resulted from carryig out the steps i the support article worked as advertised, but it forced admiistrators to elist a developer to make what should have bee a basic admiistrative chage. Admiistrative Capabilities with PowerShell With the arrival of PowerShell o the scee, the sigle-use commad lie applicatios just described have become largely a thig of the past. For example, suppose you wat to specify a sigle custom 404 page called Custom404.htm for all Web applicatios i your farm where a error page had t yet bee assiged. Istead of creatig a commad lie applicatio as described i the Microsoft support article, you could simply ope the SharePoit 2010 Maagemet Shell ad execute the followig sequece of PowerShell commads: Get-SPWebApplicatio Where-Object {$_.FileNotFoudPage -eq $NULL} ForEach-Object {$_.FileNotFoudPage = "Custom404.htm"; $_.Update()}

356 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 339 That s it. Executig oe cotiuous sequece of PowerShell commads assigs Custom404.htm for use by all Web applicatios that do t have a custom file ot foud error page assiged to them. Observat readers may recogize the ew Get-SPWebApplicatio PowerShell cmdlet from Chapter 10. The FileNotFoudPage property, though, is t oe you ca easily fid i Share- Poit s PowerShell cmdlet documetatio. The property is oe of may that are readily available for use, though, provided you uderstad a bit about the SharePoit object model. Although the SharePoit applicatio programmig iterface (API) is where developers sped quite a bit of their time, admiistrators ca still leverage the API as eeded. With PowerShell, you have complete access to all the methods ad properties that are exposed by each of the types i the SharePoit object model ad the.net Framework. The ew SharePoit 2010 PowerShell cmdlets expose some of the more useful types, methods, ad properties for you to use, but they do t cover everythig. There is far more for you to exploit if you re willig to sped some time gettig your hads dirty i the SharePoit object model. The tasks that you ca tackle with PowerShell are expasive provided you uderstad a little bit about developmet, object models, ad how all the associated pieces fit together. This chapter provides you with the overview you eed for employig disaster recovery related types ad operatios i your custom scripts or applicatios for SharePoit. To quote Ley Nero from the movie Strage Days: Are you begiig to see the possibilities here? The Disclaimer As the cover states, this is a book about SharePoit disaster recovery. It is ot a book that is dedicated to coverig all the may facets of SharePoit developmet. Much as other books cover the topic of disaster recovery i a sectio or chapter, so too does this book cover custom developmet ad associated cocers. There is a limit to the amout of iformatio ad guidace that ca be preseted i oe chapter, so a coscious decisio was made to steer clear of geeral developmet topics ad istead stay focused o those aspects of the SharePoit object model that are most applicable to the topic of disaster recovery. I additio, patters ad techologies that ca be leveraged directly for disaster recovery purposes are covered where appropriate. Some topics are also discussed i a restricted fashio to simply provide a awareess of optios available to you. These topics, although relevat to disaster recovery applicatio desig, are simply too complex or deep to cover i depth give chapter size ad time costraits. Source code ad scripts are provided oly isofar as is expediet ad eeded to illustrate a cocept or poit. Geeral best practices for SharePoit developmet, such as the use of Features to deploy code, the packagig of compoets ito SharePoit Solutio Packages (also kow by their file extesio as.wsp files), ad which objects should ad should ot be explicitly disposed

357 340 SharePoit 2010 Disaster Recovery Guide of, are abset from this chapter. These practices still apply; they simply are t discussed. May good books cover these topics i detail. If you re serious about SharePoit developmet, buy oe of them. The Price of Admissio The screeshots, examples, ad code samples i this chapter were put together i a testig eviromet with the followig software ad cofiguratio. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 R2 Eterprise Editio (build ) Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 Cliet Web browser. Iteret Explorer 8 (versio ) Developmet eviromet. Visual Studio 2010 Ultimate (versio RTMRel) SharePoit. SharePoit Server 2010 RTM with Eterprise Cliet Access Licese (build 4763) I additio to a eviromet that ca be used for developmet ad testig, we recommed that you equip yourself with a referece to the SharePoit 2010 API. Microsoft maitais a olie versio of the SharePoit software developmet kit (SDK) that is appropriate for this purpose, ad it publishes a dowloadable versio of the SDK that is periodically updated. You ca access both the olie ad dowloadable versios of the SDK through Microsoft s SharePoit Developer Ceter at The SharePoit Object Model Despite SharePoit s wealth of tools ad fuctioality, there is still more that you ca do to ehace ad exted its feature set. Luckily, SharePoit 2010 is othig if ot extesible. Although both SharePoit Foudatio 2010 ad SharePoit Server 2010 offer ample features ad capabilities, it s fairly commo to work with the platform ad after a while wish that it did just this oe thig differetly or that it took certai capabilities a bit further tha it does. If your disaster recovery eeds are ot met by SharePoit s out-of-the-box feature set ad you re i the realm of thikig about how a particular feature could be made better, custom developmet optios are probably worth explorig. This sectio explores some of the more logical disaster recovery extesio poits for the Share- Poit object model ad how you might utilize them. This chapter employs umerous domaispecific cocepts ad a sigificat degree of developmet termiology, so some fluecy with.net developmet, object model hierarchies, ad object-orieted programmig is a defiite plus. Eve without this kowledge, though, there is cotet i each sectio that ca boost your uderstadig of how SharePoit carries out its backup/recovery ad export/import operatios.

358 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 341 Extedig Catastrophic Backup ad Restore Through the SharePoit API Whe you are iterested i workig with farm-level backup ad recovery operatios, the most logical place to focus your attetio is o SharePoit s catastrophic backup ad restore types. Catastrophic backup ad restore operatios focus o the compoets of a SharePoit farm that reside at the cotet database level ad higher i SharePoit s logical hierarchy. This icludes the farm itself, Service Applicatios, Web applicatios, ad additioal objects that are either associated with or the direct childre of these compoets. The Cetral Admiistratio site exposes a iterface to these types through its Farm Backup ad Restore fuctios. SharePoit 2010 also exposes these types through a variety of cmdlets such as Backup-SPFarm, Restore-SPFarm, Get-SPBackupHistory, Backup-SPCofiguratioDatabase, ad several others. SPBackupRestoreCosole ad Related Types Whe SharePoit backups are cofigured ad executed, whether through PowerShell or the Cetral Admiistratio site, they leverage the SPBackupRestoreCosole class withi the SharePoit object model ad the types with which it is associated. Custom applicatios seekig to orchestrate backup ad restore operatios for SharePoit direct most of their calls through the SPBackupRestoreCosole class i some fashio. Although ot a true static class, SPBackupRestoreCosole largely behaves like oe. Oly oe istace of the class exists at ay give time withi the scope of the SharePoit farm, ad the bulk of its members ad properties are static. Backup ad restore operatios, job history operatios, ad iformatioal requests such as the amout of disk space a particular backup operatio may cosume all begi with calls to the SPBackupRestoreCosole. You ca fid the SPBackupRestoreCosole ad primary related types i the Microsoft. SharePoit.Admiistratio.Backup amespace withi the Microsoft.SharePoit.dll assembly. The relatioship of key types withi the amespace to oe aother is represeted by the Uified Modelig Laguage (UML) diagram show i Figure The circled umbers withi the diagram represet several types, patters, ad iteractios worthy of metio: 1. As metioed, the SPBackupRestoreCosole type is the etry poit ito catastrophic backup ad restore operatios origiatig at the SharePoit farm level. With methods such as CreateBackupRestore, DiskSizeRequired, GetHistory, ad Ru, SPBackup- RestoreCosole is capable of queuig, moitorig, ad directig all farm ad compoet-level catastrophic backup ad restore activities. 2. Oe or more SPBackupRestoreHistoryObject istaces ca be retrieved via call to the GetHistory method o the SPBackupRestoreCosole. Objects of this type provide all

359 342 SharePoit 2010 Disaster Recovery Guide Figure 11.1 Relatioships betwee the SPBackupRestoreCosole ad associated types. the iformatio eeded to determie if a backup succeeded or failed, whe it was attempted, who iitiated it, ad more. 3. The preparatio for actual backup or restore operatios typically employs a derived type from the SPBackupRestoreSettigs abstract class (SPBackupSettigs ad SPRestoreSettigs for a backup or restore, respectively) ad a SPBackupRestore- CosoleObject istace. Geerally speakig, you prepare a istace of the appropriate SPBackupRestoreSettigs subclass to idetify the locatio ad type of backup or restore to be performed. Executio of the CreateBackupRestore method o the SPBackupRestoreCosole returs a globally uique idetifier (GUID) that ca be used for the bulk of the remaiig backup, restore, queryig, ad related operatios. Sice the SPBackupRestoreCosole oly processes oe backup or restore at a time, the GUID serves as the idetifier eeded to direct the SPBackupRestoreCosole to act o the associated SPBackupRestoreCosoleObject istace. 4. Istaces of SPBackupRestoreObject are composite objects that idetify a particular item for backup or restore (such as a Service Applicatio or a cotet database) ad possibly referece childre (also SPBackupRestoreObject types) that are below them withi the backup/restore hierarchy. Oe root SPBackupRestoreObject exists

360 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 343 represetig the etire farm, ad a umber of subordiate SPBackupRestoreObject istaces represet the child compoets that are selectable for backup or restore, such as Web applicatios, services, ad so o. The hierarchy represeted by the collectio of composite SPBackupRestoreObject istaces reflects the farm s catastrophic compoet backup ad restore hierarchy. A example demostratig the basics of how to orchestrate a full-farm catastrophic backup usig the types ad techiques described appears i Listig Although fuctioal, the example is just a startig poit ad omits a umber of steps such as backup locatio free space checkig, subfarm compoet selectio, ad other items that are importat i a productio implemetatio. Note: The code show i Listig 11.1 assumes that the Microsoft.SharePoit.dll assembly is refereced ad that the Microsoft.SharePoit.Admiistratio. Backup amespace has bee imported for use by the ExecuteFarmBackup method. I additio, the Visual Studio project cotaiig the ExecuteFarmBackup method should be cofigured to target the.net Framework 3.5 o a x64 platform. Listig 11.1 public static void ExecuteFarmBackup() { // They are set through code i this example, but ormally you should give // users the optio to specify the backup locatio ad method (whether full // or differetial). Strig BACKUP_LOCATION Strig BACKUP_METHOD = SPBackupMethodType.Full.ToStrig(); // This creates a usable set of backup settigs eeded to get a backup operatio // goig. The resultat settigs object is a combiatio of the assiged // values for locatio ad method plus default values for backup thread // cout, cotet + cofiguratio backup, ad so o. SPBackupSettigs backupsettigs = SPBackupRestoreSettigs.GetBackupSettigs (BACKUP_LOCATION, BACKUP_METHOD); // Actually create (but do t start) the backup job. This registers the job with // the SPBackupRestoreCosole. Future refereces to the job are doe usig the // GUID that is retured. Guid backupguid = SPBackupRestoreCosole.CreateBackupRestore(backupSettigs);

361 344 SharePoit 2010 Disaster Recovery Guide try { // The SPBackupRestoreCosole ca execute oly oe job at a time, so // this call is a way of brigig the SPBackupRestoreCosole to focus // o the ew backup job. If aother job is ruig, the call fails // ad a exceptio is throw. if (!SPBackupRestoreCosole.SetActive(backupGuid)) { throw ew Exceptio("Backup or restore already i progress."); } } // Actually execute a full-farm backup sychroously. The call wo t // retur util the backup is complete. if (!SPBackupRestoreCosole.Ru(backupGuid, ull)) { throw ew Exceptio("Full farm backup failed. Check spbackup.log."); } } fially { // The backup job completed i some form, so the associated job GUID should // be removed for "good SharePoit hygiee." SPBackupRestoreCosole.Remove(backupGuid); } It s worth explicitly statig that the full-farm catastrophic backup set that is the output of this backup code sample is completely iteroperable with both Cetral Admiistratio s farm-level restore capabilities ad SharePoit s Restore-SPFarm PowerShell cmdlet. Oe potetial applicatio that might leverage this portio of the SharePoit object model jumps out immediately: a ew user iterface (UI) for SharePoit s catastrophic backup ad restore operatios. Although the Cetral Admiistratio site ad PowerShell cmdlets provide mechaisms for full farm backups ad restores, they are limited i both their UI ad reportig. You could develop a applicatio that delivers a rich user experiece ad does sigificatly more moitorig ad reportig tha the built-i tools. Such a applicatio could also offer greater cotrol ad access to reports regardig previous backup ad restore attempts. I additio, the hypothetical applicatio could iterface with schedulig systems such as Widows Task Scheduler to maage scheduled farm backups that operate outside the realm of SharePoit. I essece, you could create a more robust, more iteractive experiece for farm-level SharePoit backups ad restores.

362 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 345 Cotet Compoets ad Implemetig IBackupRestore By default, SharePoit is capable of backig up ad restorig a variety of compoet types: etire farms, Service Applicatios, Web applicatios, ad more. Each of these objects that ca be backed up ad restored is kow as a cotet compoet ad is represeted by a SPBackupRestoreObject istace, as show i Figure As show i Figure 11.1, a SPBackupRestoreObject cotet compoet refereces additioal types that drive its backup ad restore behavior. Oe required type i all cases is a object that derives from the abstract SPBackupRestoreIformatio class either a SPBackupIformatio istace or a SPRestoreIformatio istace. Both of these types covey iformatio about the backup or restore that is beig coducted, such as the backup locatio that is i use, the paret of the curret cotet compoet (a SPBackupRestoreObject istace itself), ad other relevat properties. The iformatio i these SPBackupRestoreIformatio-derived objects provides the cotet compoet with the data it eeds to uderstad ad properly carry out the requested backup or restore operatio. The secod object that a SPBackupRestoreObject refereces is aother object that implemets the IBackupRestore iterface. This IBackupRestore implemeter cotais the custom code that is executed durig the various stages of both the backup ad restore life cycles for the cotet compoet. I the case of a backup, for istace, the object must provide implemetatio logic for methods such as OPrepareBackup, AddBackupObjects, ad OBackup. Uder ormal operatios, a oe-to-oe mappig exists betwee a derived type of the SPBackupRestoreIformatio class ad a associated IBackupRestore implemetatio for ay give SPBackupRestoreObject. Because both SPBackupIformatio ad SPRestoreIformatio are sealed types, ad the SPBackupRestoreObject itself is a sealed type, your ability to customize ad exted the backup ad restore capabilities of SharePoit to iclude custom objects lies with the IBackupRestore iterface ad types that implemet it. To uderstad how this could be useful, cosider a couple of examples: Web.cofig files. As discussed i Chapter 5, Widows Server 2008 Backup ad Restore, you must implemet a strategy for the backup ad restore of critical system files alogside SharePoit s ow backup ad restore mechaisms to esure complete coverage of all critical ad depedet SharePoit farm targets. Web.cofig files are so closely tied to SharePoit Web applicatios that may would prefer a mechaism that couples web.cofig files to their Web applicatios whe SharePoit backup ad restore operatios are performed. Associated databases. I some eviromets, it is ot ucommo to fid additioal SQL Server databases that are both used by SharePoit ad housed i the SQL Server istaces supportig SharePoit. Such databases could be critical to some facet of farm operatios, but

363 346 SharePoit 2010 Disaster Recovery Guide custom databases (that is, those that are ot SharePoit cotet databases) are ot icluded withi SharePoit s backup ad restore operatios by default. I both of the examples just cited, creatio of a cotet compoet that implemets IBackup- Restore ca be a aveue to the iclusio of the desired items (web.cofig files ad custom databases) i SharePoit s catastrophic backup ad restore operatios. Creatio of types that implemet IBackupRestore is a ivolved process that goes sigificatly deeper tha this chapter is able to cover i a step-by-step fashio. Microsoft provides a iformative walk-through o the creatio of these types i the SharePoit Foudatio 2010 SDK, though. Look for the How to: Create a Cotet Class That Ca Be Backed Up ad Restored sectio i either the olie or dowloadable versio of the SDK for more iformatio. Cofiguratio-Oly Backup ad Restore New to SharePoit 2010 is the cocept of cofiguratio-oly backup ad restore. I essece, this process allows you to capture the portable cofiguratio ad settigs that are preset i oe farm ad apply them i aother farm as a sort of template. Techically, a cofiguratio-oly restore ca also be performed to the same farm from which the backup was performed to roll back affected settigs to a earlier poit i time. From a developmet stadpoit, the creatio of types that support cofiguratio-oly backup ad restore is similar to the creatio of custom cotet compoets for backup ad restore. Much like the creatio of a custom cotet compoet, a SPBackupRestoreObject ad a SPBackupRestoreIformatio-derived type are i play whe a custom cofiguratio compoet is backed up ad restored. As you might guess from lookig at Figure 11.1, the major differece rests with the IBackupRestoreCofiguratio iterface. Custom cofiguratio compoets implemet the IBackupRestoreCofiguratio iterface istead of the IBackupRestore iterface, ad it is through the CaBackupRestoreAsCofiguratio property o the iterface that they sigal their ability to participate i cofiguratio-oly backup ad restore operatios. Classes that implemet IBackupRestoreCofiguratio must represet truly portable cofiguratio data ad other iformatio that is ot specific to a particular server, farm topology, or other similar aspect of a SharePoit eviromet. I additio, eve though IBackupRestore- Cofiguratio implemeters participate i both cofiguratio-oly ad stadard cofiguratiowith-cotet backups ad restores, they themselves must ot cotai aythig that represets farm cotet, such as site collectios, lists, list items, supplemetal databases, ocofiguratio files, ad so o. The Special Case of Web Service Applicatios Web Service Applicatios (derived from SPIisWebServiceApplicatio) ad Web Service Applicatio proxies (derived from SPIisWebServiceApplicatioProxy) are ew to SharePoit

364 Chapter 11 SharePoit 2010 Disaster Recovery Developmet ad represet a special case whe it comes to catastrophic backup ad restore. Support for backup ad restore operatios is t supplied by the stadard catastrophic types that reside i the Microsoft.SharePoit.Admiistratio.Backup amespace, but rather through a few specific types i the Microsoft.SharePoit.Admiistratio amespace that are part of the Service Applicatio Framework. Note: The Service Applicatio Framework does ot participate i cofiguratio-oly backups ad restores oly cotet-plus-cofiguratio backup ad restore operatios. If you create your ow Web Service Applicatios ad proxies ad wat to iclude them i backup ad restore operatios, kow that the creators of the Service Applicatio Framework have already doe most of the heavy liftig for you. Ulike the process of implemetig the IBackupRestore iterface for custom cotet compoets, Web Service Applicatios ad their proxies ca be icluded i backup ad restore operatios with the assigmet of oe of the followig attributes at the applicatio class level: IisWebServiceApplicatioBackupBehaviorAttribute for Web Service Applicatios IisWebServiceApplicatioProxyBackupBehaviorAttribute for Web Service Applicatio proxies Whe you use these attributes, the Service Applicatio Framework automatically takes care of backig up ad restorig the followig resource types that are tied to your Web Service Applicatios ad proxies: Persisted objects Platform-level access cotrol lists Service edpoits Associated applicatio pools Topology service-based load balacers Databases ad roud-robi load balacers refereced through SPDatabase-derived classes If your Web Service Applicatios or proxies maitai custom resources that should be backed up ad restored, such as load balacers that do t derive from the SPDatabase type, you eed to do some custom codig. Neither the IisWebServiceApplicatioBackupBehaviorAttribute or the IisWebServiceApplicatioProxyBackupBehaviorAttribute type is sealed, ad you ca exted them to support the iclusio of custom resources i the backup ad restore process.

365 348 SharePoit 2010 Disaster Recovery Guide Figure 11.2 Similarities betwee IisWebServiceBackupBehaviorAttribute ad IBackupRestore. Both of these attributes derive from the IisWebServiceBackupBehaviorAttribute abstract type. As show i Figure 11.2, the IisWebServiceBackupBehaviorAttribute icludes may of the methods ad properties that the IBackupRestore iterface uses for custom cotet compoet protectio. Whe you execute backups ad restores, iteractios with protected Web Service Applicatios ad proxies occur i much the same way that custom cotet compoets are egaged through the IBackupRestore iterface. It is worth otig that backups for Web Service Applicatios ad proxies are supported by Microsoft oly whe they re doe through the use of the IisWebServiceApplicatioBackup- BehaviorAttribute ad IisWebServiceApplicatioProxyBackupBehaviorAttribute attributes. It is oly through the use of these attributes that certai elemets, such as servicerelated applicatio pools, ca be properly backed up ad restored. Export, Import, ad Associated Types Catastrophic backup ad restore types are t the oly optios available to you whe you re tryig to capture SharePoit data programmatically. Export ad import types are also available, but they operate i a sigificatly differet fashio. The Cotet Deploymet API SharePoit s Cotet Deploymet API, also kow as the PRIME API (iterally at Microsoft), offers aother set of tools ad approaches for preservig ad migratig SharePoit cotet ad

366 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 349 Figure 11.3 Relatioships betwee key Cotet Deploymet types. structure. The bulk of the Cotet Deploymet API types live i the Microsoft.SharePoit. Deploymet amespace. The UML show i Figure 11.3 represets the key types withi the amespace: Out of the box, the SharePoit platform leverages the Cotet Deploymet API i differet ways ad areas. Here are just a few: PowerShell. Both the Export-SPWeb ad Import-SPWeb cmdlets leverage the Cotet Deploymet API to carry out their export ad import operatios. SharePoit Server Cotet Deploymet. Available as a feature withi SharePoit Server (ot SharePoit Foudatio), Cotet Deploymet permits admiistrators to defie deploymet paths (sources ad destiatios) ad jobs (scheduled executios) for the movemet of site cotet from oe site collectio to aother. This is commoly used i publishig scearios to push cotet from a authorig farm to a productio farm. Cetral Admiistratio Graular Backup. The ability to export site collectios, sites, ad lists from withi the Cetral Admiistratio site relies o the Cotet Deploymet API. As implied by the descriptios thus far, the Cotet Deploymet API does ot operate from the classic perspective of backup ad restore; rather, the cotet deploymet classes approach site persistece with the goal of copyig from oe site ad importig ito (or mergig with) aother. It is easier to thik of backup ad restore as a cloig process: that which is restored matches that which was backed up. That is t the case with the Cotet Deploymet API. Depedig o

367 350 SharePoit 2010 Disaster Recovery Guide how a export ad import are ru, how associated depedecies are hadled, whether or ot cotet already exists i the destiatio site, ad so o, the results o the import side of a export/import operatio set may differ sigificatly from the export source. This teds to make the Cotet Deploymet API less suited to full-fidelity backups ad more useful for exportig portios of a site, mergig cotet o import, ad more. For basic export ad import fuctioality, though, the Cotet Deploymet API is relatively easy to use. A example demostratig the export of a sigle SharePoit site (that is, a SPWeb) is show i Listig Note: The code show i Listig 11.2 assumes that the Microsoft.SharePoit.dll assembly is refereced ad that the Microsoft.SharePoit.Deploymet amespace has bee imported for use by the ExecuteSiteExport method. I additio, the Visual Studio project cotaiig the ExecuteSiteExport method should be cofigured to target the.net Framework 3.5 o a x64 platform. Listig 11.2 public static void ExecuteSiteExport() { // Establish values to cover the basics of the export operatio that is goig // to be performed. The site ad locatio variables are fairly self-explaatory. // Because cotet exports ca result i the creatio of more tha oe file, the // curret variable value (below) may yield FreshNewsExport.cmp, FreshNewsEmport2.cmp, // FreshNewsExport3.cmp, etc., series depedig o how much cotet exists for export. Uri sitetoexport = ew Uri(" Strig exportlocatio Strig exportfileamebase // The SPExportSettigs object defies the export operatio to perform. You ca exercise // a great deal of cotrol over the export operatio with the SPExportSettigs // collectio of properties. SPExportSettigs basesettigs = ew SPExportSettigs(siteToExport, exportlocatio, exportfileamebase); basesettigs.exportmethod = SPExportMethodType.ExportAll; basesettigs.filecompressio = true; basesettigs.filemaxsize = 256; basesettigs.icludesecurity = SPIcludeSecurity.All; basesettigs.icludeversios = SPIcludeVersios.All;

368 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 351 } // SPExport actually carries out the export operatio. The type raises a umber of // evets that ca be tapped, if desired, to respod to export chages ad progress // otificatios. Because SPExport implemets IDisposable, it eeds to be disposed of // properly with either a usig block (as see below) or with a explicit Dispose call. usig (SPExport exporter = ew SPExport(baseSettigs)) { exporter.ru(); } The result of ruig the code show i Listig 11.2 is a sigle FreshNewsExport.cmp file at the selected export locatio provided the cotet i the site is less tha roughly 256MB followig compressio. The FileMaxSize property defies how big each.cmp file is allowed to get before the file is closed ad a ew oe is opeed for export. If the FileMaxSize property were assiged a value of 32 ad a total of 100MB of cotet (postcompressio) existed i the site to be exported, approximately three files would be created at the export locatio: FreshNewsExport.cmp, FreshNewsExport2.cmp, ad FreshNewsExport3.cmp. Approximately is specified because SharePoit s ability to break a export ito chuks of the desired size depeds o the cotet that s actually goig ito the files. The total umber of files ad their size ca vary from export to export. You ca leverage the Cotet Deploymet API i other ways as well. You ca use it to execute icremetal exports, support path updatig o imports, export with compressio to produce loose file sets, ad more. I specific situatios, it may be of greater use ad applicatio tha the catastrophic backup ad restore types of the Microsoft.SharePoit.Admiistratio. Backup amespace. The SharePoit PowerShell cmdlets described i Chapter 10 that execute exports ad imports leverage the Cotet Deploymet API; you ca geerate ad use export packages iterchageably betwee the two. You ca use exports that are created usig the types i the Microsoft. SharePoit.Deploymet amespace with the Import-SPWeb PowerShell cmdlet without issue. You ca import the site collectio, site, ad list exports that you geerate usig Cetral Admiistratios graular backup capabilities ito a site usig types that reside withi the Microsoft. SharePoit.Deploymet amespace. This also holds true for imports that are geerated usig the Export-SPWeb PowerShell cmdlet. Site Collectio Backup ad Restore Thus far you have bee itroduced to two differet approaches that the SharePoit object model offers for data capture ad protectio. At oe ed of the spectrum sits the catastrophic backup ad restore capabilities that are provided by types that reside primarily withi the Microsoft. SharePoit.Admiistratio.Backup amespace. At the other ed of the spectrum are the cotet duplicatio ad migratio fuctios that are exposed by the types i the Microsoft.

369 352 SharePoit 2010 Disaster Recovery Guide SharePoit.Deploymet amespace. Sittig somewhere i betwee both of these is the SPSiteCollectio type. The Somewhat Uusual Case of the SPSiteCollectio Type The Backup ad Restore methods of the SPSiteCollectio type are resposible for carryig out the site collectio backup ad restore operatios you might expect them to. Microsoft cosiders these operatios part of the SharePoit graular backup ad export architecture, but they do t quite fit the modus operadi of the other export ad import types i the Deploymet amespace. I fact, the SPSiteCollectio type resides withi the Microsoft. SharePoit.Admiistratio amespace ad does t iteract at all with the Cotet Deploymet API. At the same time, the SPSiteCollectio type does t iteract with the catastrophic backup ad restore types i the Microsoft.SharePoit.Admiistratio.Backup amespace. This lack of couplig to catastrophic backup ad restore is further evideced by the fact that the SPSite- Collectio type does t implemet the IBackupRestore iterface, which is the hallmark of a cotet compoet. Note: At first glace you might thik that the SPSiteCollectio type represets a sigle site collectio. I actuality, it represets a collectio of SPSite objects that is, a collectio of site collectios. It is a admiistratio object that is typically used to maipulate the site collectios that are associated with a particular Web applicatio (SPWebApplicatio). If you dig deep eough ito the SharePoit object model, you fid that the SPSiteCollectio Backup ad Restore methods drill through to the BackupSite ad RestoreSite methods o SharePoit s core SPRequest type. The BackupSite ad RestoreSite methods are basically othig but thi wrappers aroud exteral calls to SharePoit s legacy compoet object model (COM) ifrastructure, meaig the actual site collectio backup ad restore operatios are hadled i opaque (ad basically utouchable) umaaged code. Leveragig Site Collectio Backup ad Restore Although the uderpiigs of the site collectio backup ad restore operatios are based i COM, you ca still employ these operatios through the SPSiteCollectio type. I fact, site collectio backups ad restores are the easiest of all backup ad restore operatios to ru. Each oly ivolves a sigle method call ad o depedet objects, as demostrated i Listig Note: The code show i Listig 11.3 assumes that the Microsoft.SharePoit.dll assembly is refereced ad that the Microsoft.SharePoit.Admiistratio amespace has bee imported for use by the ExecuteSiteCollectioBackup method. I

370 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 353 additio, the Visual Studio project cotaiig the ExecuteSiteCollectioBackup method should be cofigured to target the.net Framework 3.5 o a x64 platform. Listig 11.3 public static void ExecuteSiteCollectioBackup() { // Establish the variables that are used to drive the backup operatio. The // variables are assiged directly here, but a more practical applicatio of // the Backup method ivolves values beig passed ito the method. Strig backupfileame Strig sitecollectiourl Boolea overwriteifexistig = true; // The Web applicatio that hosts the site collectio of iterest is t kow // directly, so it is looked up. The code the uses that Web applicatio s // SPSiteCollectio (from the Sites property) for the Backup operatio. SPWebApplicatio hostigwebapp = SPWebApplicatio.Lookup(ew Uri(siteCollectioUrl)); SPSiteCollectio associatedspsites = hostigwebapp.sites; } // Execute the actual backup operatio to geerate the backup file. associatedspsites.backup(sitecollectiourl, backupfileame, overwriteifexistig); Restorig a site collectio backed up i this fashio is as simple as chagig the Backup method call to a Restore method call. Eve the method parameters ad their orderig remai the same betwee calls. Backups created i this fashio are writte out as a sigle file, which further drives home the differeces betwee backups performed i this fashio ad those that are performed through the Microsoft.SharePoit.Admiistratio.Backup amespace; specifically, o backup ad restore history is maitaied for operatios carried out through the SPSiteCollectio type. Loggig of backup ad restore operatios is ot performed, either, makig use of the SPSite- Collectio type more of a lightweight approach to backup ad restore operatios. Use of the SPSiteCollectio.Backup geerates the same type of file output as that which is geerated whe ruig a site collectio backup from Cetral Admiistratio or a site collectio backup usig the SharePoit Backup-SPSite PowerShell cmdlet. You ca restore site collectios geerated usig the code i Listig 11.3 with the Restore-SPSite cmdlet. By the same toke, you ca restore site collectio backups that are created usig Cetral Admiistratio s site collectio backup operatio or the Backup-SPSite PowerShell cmdlet with the SPSiteCollectio.Restore method.

371 354 SharePoit 2010 Disaster Recovery Guide As a example of where you could leverage the SPSiteCollectio type particularly effectively, cosider the followig sceario. Out of the box, oly farm admiistrators or those who possess admiistrative-level access to the servers that SharePoit rus o ca execute SharePoit backups. Because you ca easily execute site collectio backups from withi a SharePoit site through custom code leveragig the SPSiteCollectio type, you ca develop a solutio to give site admiistrators the capability to execute o-demad backups for site collectios for which they have some resposibility. Such a solutio might take the form of a custom admiistrative actio, user cotrol, or Web Part, ad you ca eable or disable it for specific groups ad idividuals as goverace policies demad. Programmatically Usig SQL Sapshots As described i Chapter 7, SQL Server 2008 Backup ad Restore, SQL Server Developer ad Eterprise editios iclude support for database sapshots. Although this support has bee preset i the SQL Server product sice SQL Server 2005, it is oly with the 2010 platform that a awareess of sapshots exteds to SharePoit. Now that SharePoit is aware of SQL Server s database sapshot fuctioality, you ca leverage that fuctioality i code that you write. The SPDatabase type i the Microsoft.SharePoit.Admiistratio amespace represets a SQL Server database, ad SharePoit uses SPDatabase ad its derived types to read, write, ad maipulate the cotets of databases that are used by the farm. Particularly oteworthy amog the SPDatabase-derived types is the SPCotetDatabase type, which represets a cotet database housig site collectios. I SharePoit 2010, the SPDatabase type has bee exteded with a Sapshots property. As show i Figure 11.4, the Sapshots property exposes a collectio of type SPDatabaseSapshotCollectio. Through the Sapshots collectio ad each of its SPDatabaseSapshot items, it is possible to create, delete, ad maage SQL Server sapshots for the database i the uderlyig SQL Server istace. Whe a sapshot is created, either programmatically through the SharePoit object model or directly through SQL Server, that sapshot is treated as if it were a completely differet readoly database o SQL Server. Although sapshots are commoly created from live SharePoit cotet databases, they are ot attached to the SharePoit farm. Because the sapshots are t affiliated with a SharePoit farm, you eed to use the ew uattached cotet database model (through the SPCotetDatabase.CreateUattachedCotetDatabase method) to iteract with them. Listig 11.4 demostrates the same site collectio backup operatio that was show i Listig 11.3, but it shows how you ca use a database sapshot to ehace the overall backup process. By executig the SPSiteCollectio.Backup operatio agaist a database sapshot istead of the live cotet database, there is o eed to lock the live database while the backup is beig

372 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 355 Figure 11.4 Database sapshot support for SPDatabase ad derived types. performed. Users ca cotiue to coduct read ad write operatios as they ormally would, ad the backup operatio ca proceed agaist the sapshot without worries of corruptio or icosistecies. Whe the backup operatio is complete, the sapshot is deleted to free ay resources it held o SQL Server. Note: The code show i Listig 11.4 assumes that the Microsoft.SharePoit.dll assembly is refereced ad that the Microsoft.SharePoit, Microsoft.Share- Poit.Admiistratio, ad Microsoft.SharePoit.Admiistratio.Backup amespaces have bee imported for use by the ExecuteSiteCollectioBackup- WithSapshot method. I additio, you should cofigure the Visual Studio project cotaiig the ExecuteSiteCollectioBackupWithSapshot method to target the.net Framework 3.5 o a x64 platform.

373 356 SharePoit 2010 Disaster Recovery Guide Listig 11.4 public static void ExecuteSiteCollectioBackupWithSapshot() { // As with the ExecuteSiteCollectioBackup method, these variable values // would ormally be supplied to the method rather tha set here. Strig backupfileame Strig sitecollectiourl Boolea overwriteifexistig = true; // These two variables are set with properties from the SPSite object that // is created. To miimize the size of the usig block that follows, the // variables are scoped here. SPCotetDatabase housigdb; Strig rootrelativeurl; // Obtai the critical property values that are eeded from the SPSite. usig (SPSite sitetobackup = ew SPSite(siteCollectioUrl)) { // The cotet database that houses the site collectio is eeded to // geerate a sapshot. The relative site collectio URL // is eeded for the evetual uattached DB backup operatio. housigdb = sitetobackup.cotetdatabase; rootrelativeurl = sitetobackup.serverrelativeurl; } // Oly Developer ad Eterprise versios of SQL Server support sapshots. If // sapshots are t supported, the process ca t cotiue. if (!housigdb.sapshots.issapshotsupported) { throw ew NotSupportedExceptio("Sapshots ot supported."); } // Each SPDatabase-derived type (icludig SPCotetDatabase) has a Sapshots // collectio that serves as the gateway to workig with sapshots. Refresh // the collectio ad the use it to create a ew sapshot. SPDatabaseSapshotCollectio allsapshots = housigdb.sapshots; allsapshots.refreshsapshots(); SPDatabaseSapshot hostigdbsapshot = housigdb.sapshots.createsapshot(); // Oce SQL Server creates the sapshot, it s just like ay other database. // SharePoit s uattached cotet database fuctioality is used to attach to // the sapshot as if it were a read-oly cotet database.

374 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 357 SPCotetDatabase sapshotdb = SPCotetDatabase.CreateUattachedCotetDatabase (hostigdbsapshot.coectiostrig); // With a valid SPCotetDatabase referece, the collectio of site collectios // i the sapshot ca be refereced ad used to perform the site collectio backup. SPSiteCollectio sitesisapshot = sapshotdb.sites; sitesisapshot.backup(rootrelativeurl, backupfileame, overwriteifexistig); } // Whe the backup operatio is over, delete the sapshot to istruct SQL Server // to release the resources associated with it. hostigdbsapshot.delete(); A partig word of cautio regardig the use of sapshots is warrated. Listig 11.4 icludes a call to the RefreshSapshots method to esure that the collectio of SPDatabaseSaphot objects is curret prior to ay collectio maipulatio activities. This is doe because there are regular processes withi SharePoit Foudatio, such as the Microsoft SharePoit Foudatio Sapshot Maagemet timer job, that ca create ad delete database sapshots. Ay SPDatabaseSapshotCollectio that has a EabledMaagemet property value of true is subject to regular sapshot maiteace by SharePoit, ad this maiteace ca lead to the additio ad deletio of sapshots durig the executio of your code. For this reaso, it is prudet to refresh the cotets of the collectio through the RefreshSapshots method before attemptig ay maipulatio of the collectio withi your code. Volume Shadow Copy Service Discussio of custom developmet for the purpose of catastrophic protectio has thus far focused o the SharePoit object model ad types it exposes for your use i backup ad restore operatios. Although these types provide a variety of ways to leverage ad exted SharePoit s built-i capabilities, they suffer from a sigificat umber of costraits. The followig are just a few: The approach that the SharePoit object model employs for backup ad restore is t particularly scalable. As a SharePoit farm grows, use of the types i the Microsoft.Share- Poit.Admiistratio.Backup amespace have a growig impact o ormal farm operatios. With extremely large farms cotaiig terabytes of cotet, executio of a built-i catastrophic backup ca literally brig a farm to its kees. All of SharePoit s catastrophic backup operatios are based o writig backup data to a file share through stadard file operatios. This is less tha desirable i may circumstaces, because the file operatios ca t be altered to icorporate ecryptio, compressio, backup locatio groomig, ad may other expected fuctios. Data that you might cosider importat for backup purposes that is t tied directly to the farm ad recogized withi SharePoit s cotet compoet hierarchy is difficult to protect.

375 358 SharePoit 2010 Disaster Recovery Guide Although it is true that SharePoit s catastrophic backup ad recovery system ca be exteded usig the IBackupRestore iterface, the IBackupRestoreCofiguratio iterface, ad attributes offered by the Service Applicatio Framework, the implemetatio tasks are far from trivial. Eve if sigificat time ad effort are ivested to create ew cotet compoets to itegrate with the built-i catastrophic backup system, the other limitatios already discussed still apply. I light of these ad other limitatios, most eterprise-scale backup systems that are desiged to protect SharePoit stay clear of the types i the Microsoft.SharePoit.Admiistratio. Backup amespace ad opt for a differet approach. I may cases, these systems leverage VSS. What Is VSS? The Volume Shadow Copy Service, or VSS, is a somewhat mysterious-soudig set of extesible backup-related APIs that Microsoft has bee developig ad evolvig sice they first appeared i Widows XP. VSS was desiged from the groud up to provide applicatios, icludig the Widows operatig system, with a mechaism for creatig cosistet poit-i-time sapshots of file system data eve if some or all of the files captured i the sapshot are i use whe the sapshot is take. You ca the use these volume sapshots as the source for backup operatios ad subsequetly dispose of them if you o loger eed them. The heart of VSS is the VSS itself. This service is implemeted as a Widows service that rus i the Local System cotext ad is started ad stopped o demad to create volume sapshots as directed. Types of Sapshots VSS is aware of the uderlyig file system at the block level, ad the built-i system provider is capable of creatig volume sapshots i either full copy or differetial copy modes. A full copy of a file system volume is exactly what its ame implies: a cloe of the data o the volume that is targeted for a shadow copy sapshot. Whe the full copy operatio is complete, the result is a shadow copy volume that exists idepedetly of the source volume ad ca be used for readoly backup operatios. Differetial copies are similar to full copies i that they result i the creatio of a read-oly shadow copy sapshot that is suitable for backup operatios, but the uderlyig executio of the sapshot process is sigificatly differet ad typically much faster. Differetial copies leverage a differecig area ad a copy-o-write system that tracks oly those blocks of data that have chaged i the origial volume sice the sapshot was take. Differecig areas start out empty because the source volume ad the sapshot volume are idetical at the time of sapshot creatio. As chages are made to the source volume durig ormal activities, the origial file system blocks (which are about to be overwritte by the ew data) are copied from the source volume to the sapshot s differecig area. As chages cotiue, the differecig area cotiues to grow to hold all the origial source volume blocks that have bee overwritte sice the sapshot was take.

376 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 359 For backup cosumers, the sapshot volume that is exposed eds up beig a combiatio of the curret source volume plus the blocks of the differecig area overlaid o top. The result is a read-oly volume that appears exactly as it did whe the differetial copy sapshot was take. VSS Compoets The optios you have available to you whe workig with VSS deped o how you ited to leverage it. To uderstad the architecture of VSS, it helps to uderstad the differet compoet types that are ivolved i the creatio of a shadow copy: VSS. As described earlier, the VSS is itegrated ito the Widows operatig system ad is resposible for exposig, orchestratig, ad coordiatig the actios of most of the other compoet types related to the creatio ad maagemet of volume shadow copies. Writer. A writer is a compoet that serves as a bridge betwee VSS ad a applicatio or service that possesses data that ca be icluded i a VSS operatio. Writers itegrate kowledge of their applicatio or service ad work with the VSS to esure that applicatios ad services are quiesced their pedig operatios are settled ad operatioal activities suspeded. This esures that applicatio ad service data is cosistet prior to VSS executig a sapshot. Writers also commoly provide some form of post-restore sychroizatio support for their applicatios or services. Writers are available for SQL Server, Hyper-V, SharePoit, Widows Maagemet Istrumetatio (WMI), the Registry, ad a multitude of other services ad applicatios. Provider. A provider is a compoet that actually carries out the shadow copy process ad maages the storage volumes that are associated with VSS operatios. Providers ca either be software based, like the built-i system provider that is supplied with the operatig system, or they ca be hardware based ad tied to their associated storage arrays. Regardless of the actual implemetatio, providers do the grut work of poit-i-time volume sapshot geeratio, maagemet of the uderlyig volumes to store the critical pieces of a sapshot (such as differecig areas), ad more. Requestor. A requestor is a applicatio that cosumes VSS for the purposes of backig up or restorig data. A good example of a VSS requestor is the Widows Server Backup applicatio that is built ito Widows Server 2008 ad described at legth i Chapter 5. Whe Widows Server Backup eeds to create a backup, it egages the VSS to geerate a sapshot of the data to be backed up. Oce VSS geerates the sapshot, Widows Server Backup creates a backup from the sapshot ad the releases it. Each of these compoet types is a critical piece i the overall architecture of VSS. Leveragig VSS for SharePoit backup operatios focuses primarily o two of the four compoet types metioed, though: writers ad requestors.

377 360 SharePoit 2010 Disaster Recovery Guide The Role of the SharePoit Foudatio VSS Writer After readig the compoet descriptio of a VSS writer ad how writers are associated with applicatios ad services, you may be woderig if SharePoit has its ow writer. If so, the aswer is yes. I fact, it techically has two. The SharePoit Foudatio VSS writer (or SPF-VSS writer) is istalled whe either SharePoit Foudatio 2010 or SharePoit Server 2010 is istalled o a server. Oce registered, the writer itegrates with the VSS ifrastructure to provide the applicatio the itelligece ad capabilities it eeds to geerate cosistet ad usable shadow copies of each of the compoets that make up a SharePoit farm. This icludes cotet databases, Service Applicatio databases, registered third-party databases, ad more. The SPF-VSS writer also works with a secodary search idex writer that is istalled at the same time as the SPF-VSS writer to provide sapshot ad restore support for SharePoit s file-based search idexes. A importat poit to ote is that the SPF-VSS writer itself does t create backups or execute restores. The VSS (i cojuctio with oe or more VSS providers) is still resposible for creatig shadow copies of the volumes housig SharePoit data, ad actual backup ad restore operatios are orchestrated by a VSS requestor. The key advatages that the SPF-VSS writer offers are based o its applicatio kowledge of SharePoit: 1. Cosistet sapshot state. Prior to VSS sapshot creatio, the SPF-VSS writer trasitios the SharePoit farm ito a cosistet state o disk. Databases are quiesced, pedig trasactios may be flushed, search idex file operatios are completed, ad the etire farm is effectively paused for a brief period to allow the VSS to geerate its sapshot. This is a critical step. If a sapshot were take of the farm i a icosistet state, there s a reasoable chace that a restore operatio that is coducted usig data i the sapshot could fail. 2. Post-restore activities. Whe a requestor or its paret applicatio restores SharePoit farm data that was backed up from a VSS sapshot, there are typically some postrestore sychroizatio steps that must be carried out to get the SharePoit farm back to a fully fuctioal state. Whe the SPF-VSS writer is otified by a requestor that a restore operatio is takig place, the SPF-VSS writer takes care of the farm sychroizatio steps oce the restore is completed. These qualities make the SPF-VSS writer a itegral part of ay backup ad restore solutio that iteds to leverage VSS for SharePoit farm protectio. Developig Solutios with VSS Without a doubt, VSS brigs a lot to the table if you are seekig to develop a eterprise-ready, scalable, robust backup ad restore store system for SharePoit. The primary compoet type of iterest for custom backup ad restore applicatio developmet is the VSS requestor. Requestors

378 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 361 are the ultimate users ad orchestrators of VSS services, ad a custom backup ad restore applicatio falls squarely ito the requestor compoet type category. Now that you re probably excited about leveragig the power of VSS, we eed to share some potetially bad ews: Microsoft does t supply ay form of maaged libraries or extesios that would allow you to use VSS i your.net applicatios. Microsoft s support for applicatio developmet agaist VSS is provided through a set of COM ad C++ types that are packaged ito the Widows SDK. This leaves you with a couple of optios: Develop your requestor i a laguage such as umaaged C++. Write or leverage a wrapper library aroud the VSS types of iterest ad geerate a rutime callable wrapper (RCW) that a.net applicatio ca cosume. This approach still requires that you do some C++ or equivalet developmet just less of it. Neither of these approaches is trivial for the average.net developer. I additio, the orchestratio of VSS operatios is tricky ad fraught with pitfalls. Creatig a sapshot is t as simple as makig a sigle call such as vss.geeratesapshot(). Writer metadata has to be gathered ad processed, writers must be elisted for sapshot operatios, depedecies across writers must be established, the sapshots have to be take ad released, ad more. The tasks ad processes are documeted i the Widows SDK, but there is a sigificat amout of material to lear ad icorporate. Tip: If you are a.net developer ad still have your heart set o workig with VSS after all that s bee said, kow that there are at least a couple of resources available to you. At a miimum, you eed to dowload the Widows SDK ad become familiar with its cotets. The quickest path to productivity lies with the AlphaVSS project o CodePlex ( though. AlphaVSS is a maaged library aroud the iterfaces you eed to work with VSS. It is well documeted ad highly istructive. It wo t make you istatly productive with VSS, but it dramatically reduces the learig curve ad work you have to do. Give the described requiremets ad complexity, a workig example of VSS i actio for SharePoit backup is well beyod the scope of this book. Rollig Your Ow Backup ad Restore Approach Each of the custom approaches discussed thus far has its ow uique set of advatages ad disadvatages. The types withi the Microsoft.SharePoit.Admiistratio, Microsoft. SharePoit.Admiistratio.Backup, ad Microsoft.SharePoit.Deploymet amespaces offer a variety of built-i capabilities for preservig ad recoverig cotet ad other importat

379 362 SharePoit 2010 Disaster Recovery Guide SharePoit data withi your farm. VSS is a prove techology that gives you a way to geerate cosistet poit-i-time sapshots for the overwhelmig majority of the SharePoit cofiguratio ad cotet data i your farm. I may cases, some combiatio of these techologies ad code approaches will prove adequate for your eeds. We clearly recogize that the approaches discussed thus far may oly get you part of the way toward achievig your ultimate goal. Just as there is o oe-size-fits-all approach to SharePoit disaster recovery, so too is there o master set of custom code that ca solve every backup ad restore eed. The two sectios that follow offer a couple of additioal techiques you may use to tackle aspects of your custom disaster recovery developmet eeds. Neither of the techiques is specific to disaster recovery developmet, but both ca be leveraged i a variety of custom developmet scearios tied to SharePoit disaster recovery. Object Model Walkig If your custom developmet sceario is focused o capturig a variable set of cotet withi the SharePoit eviromet, particularly at the site collectio or subsite collectio level, the idea of object model walkig may be of iterest to you. At a basic level, object model walkig is a geeral term for traversig hierarchically orgaized groups of objects (a object graph) to coduct some operatio o them or extract iformatio of iterest from them. For purposes of capturig ad protectig data i SharePoit, you might apply this cocept to save or restore data of iterest withi a site collectio ad some subset of its subordiate objects. I essece, this is how SharePoit s ow Cotet Deploymet API is built. Figure 11.5 demostrates a selective hierarchy of types that spa from the site collectio level (SPSite) dow to the SharePoit list level (SPList). Although the Cotet Deploymet API provides you with mechaisms for exportig from ad importig to a SharePoit site collectio, you are boud by the API s costraits ad modes of operatio. These are adequate i most cases, but they may fall short i others. Cosider the case of workflows, for example. Data that is acted o by workflows is relatively straightforward to capture, but the state of the workflows is ot. The Cotet Deploymet API does t allow you to capture or export workflow state. If the Cotet Deploymet API proves to be more of a barrier tha a buildig poit, you may decide to avoid it altogether ad come up with a custom mechaism for protectig all the data of iterest. If you elect to protect site collectios ad their data, you would likely start by examiig the site collectio (SPSite) of iterest to read ad capture all the data of iterest that is represeted by it workflows, work items, users, permissios, recycle bi iformatio, activated features, ad more. The list is extesive. Some objects ad properties ca be read directly, whereas others require the use of helper objects or predefied access sequeces.

380 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 363 Figure 11.5 Object hierarchy from SPSite to SPList. Of course, the SPSite is just the tip of the iceberg. Each SPSite cotais at least oe SPWeb object i the form of the RootWeb, ad i all likelihood the SPSite istace cotais may more SPWeb objects that are orgaized below it i a hierarchy. These SPWeb objects also have their ow properties ad collectios of objects that require processig. Some of the data ca be clealy extracted ad recostituted ito object form later, but may of SharePoit s objects ca t be created or maipulated outright; they possess costraits, depedecies, ad logic that require careful orchestratio to arrive at a poit where a recostituted object matches the state that existed at the time its origial object was persisted. Ultimately, the amout of data ad the fidelity with which it is captured is a decisio that is left completely up to you. Also left up to you is the maer i which you read, persist, load, ad reapply the cotet you are protectig. There is o predefied way to traslate SPSite, SPWeb, ad depedet objects for storage with the call of a sigle method. At the same time, re-creatig those objects i a usable form from your storage is goig to prove challegig. If you re thikig that this approach to cotet protectio souds like it could be a awful lot of work, you re absolutely right. The amout of work is tied to the fidelity with which you ited to capture ad restore data. A full-fidelity backup codebase that is based o object model walkig is certaily possible, but it would be a complex udertakig. Object model walkig i your ow code is most appropriate whe you are tryig to capture either a limited subset of Share- Poit data or data that is t captured through the catastrophic ad deploymet types.

381 364 SharePoit 2010 Disaster Recovery Guide Employig Serializatio Surrogates Serializatio surrogates are t specific to SharePoit, or are they a ew cocept to.net developmet. They come i hady, though, whe you wat to serialize class istaces that you do t cotrol the source for. To uderstad why this is applicable i the case of protectig SharePoit data, you eed to have some familiarity with SharePoit s history ad how it works uder the hood. Uder the Hood with SPRequest Although SharePoit 2010 comes with a rich object model you ca employ to address all maer of custom developmet challeges, it has a dirty little secret udereath its maaged library hood, SharePoit rus o a egie that has a sigificat chuk of COM i it. Diggig ito the Microsoft.SharePoit.dll ad the Microsoft.SharePoit.Library amespace reveals the SPRequest type. The SPRequest type is the maaged wrapper aroud a wealth of methods that are exposed by the OWSSvrLib.dll dyamic lik library. The majority of the fuctioality that is exposed to.net callers i the SPRequest type gets mapped directly through to umaaged methods i the OWSSvrLib.dll COM library. You might be woderig why the SPRequest type is so special ad merits the metio that it s gotte so far. It would be a fair questio, ad the aswer is pretty straightforward. Two of the most commo types you use whe workig with SharePoit cotet are backed by the SPRequest type. Those two types are SPSite ad SPWeb. Without SPSite ad SPWeb, the optios for workig with cotet i SharePoit grow slim pretty quickly. Serializatio Challeges You might recall from the Object Model Walkig sectio that data protectio schemes based o object model walkig are ofte challegig due to issues of persistece. Protectio of Share- Poit cotet revolves aroud the SPSite ad SPWeb types, ad both of these types cotai a dizzyig array of properties, methods, ad associated collectios. The object model graphs that begi with these types are typically deep, complicated, ad spa the boudary betwee maaged ad umaaged code. I most areas of.net developmet, deep ad complicated object graphs like the oes described are routiely dealt with usig serializatio types ad techiques. Serializatio is the process of covertig a object graph ito a form that ca be stored or trasmitted, ad deserializatio is the complemetary process of covertig the stored or trasmitted form back ito a usable object graph. Biary serializatio of objects i.net is typically hadled by the types residig i the System.Rutime.Serializatio amespace, but biary serializatio is t the oly type available to.net developers. XML serializatio is commo, as well, ad is typically used i areas such as Web service commuicatios. Because serializatio is commoly used to persist object graphs, you might be woderig why it was t metioed i the Object Model Walkig sectio. Ufortuately for SharePoit

382 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 365 developers, SPSite, SPWeb, ad may of the other types that are tied to site collectio cotet are t good cadidates for straight serializatio. The easiest way to grat a class serializatio support via.net s built-i serializatio types is to ador it with the [Serializable] attribute. This wo t work for the SharePoit types, though, because you do t cotrol the source code for those types. SPWeb ad SPSite are t sealed objects, so techically you could subclass them to create your ow derived types ad cotrol the serializatio behavior through the subclasses. This approach is less tha desirable, though, because at their core the SPWeb ad SPSite types simply were t desiged to be serialized give their COM origis. I additio, itegratig your custom derived types with other (ative) SharePoit types, methods, ad properties would prove problematic at best if possible at all. Although direct serializatio support for SharePoit types is likely a dead ed, there is a alterative. Serializatio of SharePoit Types via Surrogate The.NET Framework supports the use of serializatio surrogates whe you wat to serialize ad deserialize objects that were t origially desiged to support these activities. A serializatio surrogate is a separate class that uderstads a specific oserializable type (like the SPSite type) ad ca act as a stad-i whe serializatio requests are made to serialize or deserialize istaces of the oserializable type. To better illustrate this cocept, examie the activity diagram show i Figure 11.6 for the series of steps that are carried out whe.net is called upo to serialize a object. The brach of the diagram marked by a circled umber oe shows the path that is followed whe objects that have a surrogate are serialized. The path marked by a circled umber two shows serializatio uder osurrogate coditios. The primary beefit of serializatio surrogates whe workig with SharePoit objects is the fact that the SharePoit objects themselves are really oly passed as data for the surrogates to operate upo. The actual data that is writte out for serializatio is left up to the surrogate. Although this is coceptually similar to the straight object model walkig sceario preseted earlier, you should bear i mid that there is t a eed to create all the custom persistece plumbig ad ifrastructure i the same way that you would have to i the object model walkig case. I additio, surrogates support a umber of advaced scearios, such as surrogate selector chais ad type remappig durig deserializatio, that make them worthy of cosideratio i custom persistece scearios. Implemetig a fuctioal serializatio surrogate example is beyod the scope of this chapter. For additioal iformatio, examie the types i the System.Rutime.Serializatio amespace ad the ISerializatioSurrogate iterface i particular. For good walk-throughs ad

383 366 SharePoit 2010 Disaster Recovery Guide Figure 11.6 Paths available durig.net serializatio. examples o usig serializatio surrogates, see the Ru-Time Serializatio, Part 3 article i the September 2002 issue of MSDN Magazie at cc aspx. Desigig Applicatios for Disaster Recovery Readiess Thus far, this chapter has discussed ways to develop agaist the SharePoit object model ad similar APIs to provide fuctioality that is ot preset withi the out-of-the-box platform. This iformatio is highly relevat to the topic of disaster recovery, but there is aother area that is ofte overlooked i a discussio of disaster recovery ad custom applicatio developmet. That area ca best be summarized with the followig questio: how do you egieer a applicatio for maximum supportability i a disaster recovery situatio or sceario? Although covetioal best practices relatig to.net programmig call for the implemetatio of certai code patters, some of these patters ca actually ru couter to the bigger picture (which icludes disaster recovery) if it is take ito accout. What s best for performace, for

384 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 367 istace, ca actually operate couter to a strategy that maitais maximum supportability ad locatio portability at its core. This sectio approaches SharePoit developmet (ad.net code developmet i geeral) from a disaster recovery midset ad makes a hadful of suggestios that are cosistet with maximum recoverability, redudacy, ad supportability for most custom applicatios i the evet of a disaster. Storage of Applicatio Cofiguratio Data Nearly all applicatios, regardless of origi or itet, deped o some form of cofiguratio data for proper operatio. Cofiguratio data, i this case, is defied as data that (a) is required for proper applicatio operatio, ad (b) ca vary based o the eviromet i which the applicatio is istalled ad executed. This data ca take may forms ad be stored i may locatios, icludig the followig: Paths to file system based cofiguratio data Database sources ad their associated coectio strigs Resources describig iteral error codes ad their associated descriptios Applicatio credetials (ecrypted or ot) to access local ad remote resources Locale-specific settigs ad assemblies Refereces to assemblies that cotai shared compoets Loggig settigs ad associated reportig iformatio If capable of uatteded executio, schedules for oiteractive processig recipiets, templates, ad coditios uder which should be set Product IDs, registratios, ad other codes Versio iformatio Whe it comes to disaster recovery, the rule of thumb regardig the storage of cofiguratio data is this: if the data ca be exteralized, every reasoable attempt should be made to do so. Cofiguratio ad operatioal data should also be separated from actual applicatio logic wheever possible. Practices such as embeddig strig literals withi applicatio code are ot recommeded. Uder these guidelies, rethik custom code that demostrates a reddish-brow color withi the Visual Studio eviromet (idicative of the use of strig literals) ad declarative programmig patters. Developmet withi the.net eviromet is made substatially easier (from a disaster recovery perspective) with the use of web.cofig files for Web-based applicatios ad app.cofig

385 368 SharePoit 2010 Disaster Recovery Guide files for Widows forms applicatios. These files, which are tied to a applicatio, ca abstract the storage of applicatio-specific settigs, database coectios strigs, exteral type registratios, ad more i a way that readily supports disaster recovery. If you re leveragig these cofiguratio files, though, you must realize that the cofiguratio files are typically tied to the istallatio locatio of their associated applicatio. If the applicatio is ot istalled to a directory or drive that backup operatios support, the cofiguratio data preset i the exteralized file or files is typically lost with the applicatio i the evet of a disaster. I additio to the use of web.cofig ad app.cofig files, storage of applicatio cofiguratio data ca be exteralized through the use of a database, a separate custom settigs file (such as a XML cofiguratio file), Web services, or a host of other optios. Each optio offers a differet set of stregths ad weakesses, so the decisio regardig which to use depeds o the acceptable trade-offs. Storage of cofiguratio data i a database is attractive from a supportability ad abstractio stadpoit because the database itself is likely stadaloe ad backed up, but use of a database i this fashio ca result i a poorly performig solutio. The use of a XML file teds to be better performig, but it also teds to ecourage a custom storage scheme that is less supportable across a eterprise uless schemas are stadardized. Whe you re storig applicatio cofiguratio data for custom SharePoit solutios, both web.cofig storage ad SharePoit database storage are highly feasible optios ad should be cosidered for use based o applicatio eeds ad goverace requiremets. Because a Share- Poit site is a ASP.NET site, it s easy to store ad retrieve settigs data from web.cofig files. The SharePoit object model also icludes some specialized types (such as the SPWebCofigModificatio type) that make it easy to itegrate cofiguratio data chages durig istallatio or activatio of custom code. At the same time, may SharePoit object types represetig easily recogized etities (such as SPFarm, SPService, ad SPWeb) have a Properties collectio that ca be used to persist custom data to the associated SharePoit databases. This meas that use of the Properties collectio to store cofiguratio data for the aforemetioed types results i that data beig icluded i ay backup approach that covers the SharePoit databases. The oly proscribed optios for cofiguratio storage have bee metioed. Placig strig literals i-lie with applicatio code greatly reduces supportability ad locatio portability. Oe otable additio to the list is the Widows Registry. I the days of COM, storage of settigs i the Widows Registry was cosidered a step forward; from a disaster recovery perspective, storage of applicatio settigs i such a fashio is ot recommeded if you ca avoid it. Although curret backup mechaisms ofte capture the Registry ad its settigs, accessig ad modifyig the settigs cotaied withi the Registry is much more ivolved ad less friedly tha workig with exteral settigs files or Web services positioed for cofiguratio storage. It would be a challege to idetify circumstaces uder which the storage of SharePoit settigs i the Registry would be preferable to the use of the SPFarm.Properties collectio.

386 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 369 Storage of Trasiet ad Persistet Applicatio Busiess Data Cofiguratio data may be resposible for gettig a applicatio ruig ad idetifyig how it should iteract withi its rutime eviromet, but it is a applicatio s busiess data that is tied to the real value that the applicatio brigs to a orgaizatio. Busiess data takes may forms; the list that follows cotais just a few of the multitude of file ad data types that fall ito this category: Spreadsheets Writte documets, icludig messages Presetatios, multimedia files, ad other audio/visual assets Whereas cofiguratio data is required for a applicatio to simply execute, busiess data ca geerally be thought of as the data that is produced or cosumed i the day-to-day operatios of a applicatio. Busiess data ca be persistet ad live beyod the scope of executio of the applicatio; it ca also be trasiet or temporary data that a applicatio uses durig computatios, auto-saves, ad so o. The questio of where a applicatio should store busiess data is ot a ew oe. The followig are some recommedatios ad poits for cosideratio: Clearly separate busiess data from other data. O both servers ad cliet workstatios, a best practice is to format at least two separate logical disks for local storage requiremets. Oe logical drive typically cotais the Widows system ad program files (typically C:\), whereas aother (oftetimes E:\) cotais applicatio ad busiess data. The use of at least two separate logical drives i this fashio makes the creatio, maiteace, ad targetig of backup operatios much easier. Leverage eviromet variables. Evirometal portability ad disaster recovery are aided sigificatly whe you avoid assumptios regardig the structure of the file system hostig a applicatio. This is particularly true whe it comes to the storage of trasiet applicatio data. May applicatios eed to use the hostig system s file system for activities such as compressio/decompressio, ecryptio/decryptio, ad other stream-related operatios. I these istaces, you ca use eviromet variables that the hostig operatig system supplies to esure that proper file system locatios are employed. I the case of temporary or workig files, for istace, the %TEMP% eviromet variable defies the default temporary files locatio for users who are curretly logged oto the operatig system. Make busiess data storage locatios cofigurable. This is a extesio to the poit that was made with the previous item. Whe the storage of persistet data is a requiremet, you must provide some mechaism to permit the cofiguratio of the storage locatio. This could be somethig as commo as the Save As dialog box see throughout the Widows world, or it could be a applicatio cofiguratio file settig that drives all data to a kow locatio.

387 370 SharePoit 2010 Disaster Recovery Guide Regardless of the mechaism selected, avoid assumptios about the hostig system s file system structure at all costs. Employ etwork-available services whe possible. Disaster recovery operatios are sigificatly aided whe you ca cetralize critical busiess data for backup ad restore purposes. Traditioal file shares represet oe example of how such cetralizatio ca be achieved, but they are by o meas the oly mechaism. Databases, custom busiess services, ad eve SharePoit (through WebDAV ad the WebCliet service) ca be utilized for this purpose. Cosider the cloud. Microsoft, Amazo, Google, ad may other vedors have bee steadily icreasig the capability ad reliability of their cloud-based storage offerigs. At the same time, the tools ad APIs eeded to iteract with cloud-based storage have bee gettig easier for developers to lear ad use. Whe it comes to offsite storage that is itself redudat ad ready for disaster recovery tasks, it is well worth the time ivested to see if you ca itegrate cloud-based storage ito your desig. With SharePoit custom solutios, the storage of trasiet data should obey the poits just described. The storage of persistet busiess data, however, teds ot to be a large issue. Simply storig busiess data i SharePoit lists ad documet libraries esures that the busiess data is covered i the evet of a disaster provided you have a well-coceived, implemeted, ad tested SharePoit disaster recovery strategy. Accessig Network Resources I today s highly itercoected computig eviromets, etwork resources are a commo reality ad storage locatio for much of the data leveraged by applicatios. The followig are commo examples of etwork resources: File shares (that is, file system storage locatios ot residet o local disks) stores (POP3, IMAP) for -eabled applicatios Databases FTP sites Ay HTTP/HTTPS-eabled sites ad services (overlaid file shares, Web services, ad so o) The best support for disaster recovery scearios for etwork resources comes whe those resources are accessed through idirectio or some form of abstractio layer. Although the abstractio of such resources ca be a applicatio-specific exercise, several mechaisms are built ito commo operatig systems ad etwork stacks to decouple the amig of such resources ad services from their actual implemetatios: Domai Name Services (DNS). DNS is perhaps the most commo approach to separatig uiform resource locators (URLs) ad amespaces from actual resource implemetatios.

388 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 371 DNS is the stadard for Iteret amig. If a user supplies a commo Eglish ame (such as to a DNS server, the DNS server resolves the host ame to a IP address ( ). DNS decouples ames from IP addresses, but it comes with a cost i the form of DNS servers, icreased maagemet overhead, ad some eed to update ames ad their associated IP addresses. Distributed File System (DFS). Practically speakig, DFS ca be regarded as a file system switchboard service. Eterprise wide, DFS supports the practice of specifyig, mappig, ad redirectig etwork file paths. This approach decouples file path refereces from their uderlyig implemetatios, but it carries with it the eed for additioal maiteace ad admiistratio. SQL Server aliases. Use of a SQL Server alias creates a machie-local abstractio layer betwee a SQL Server istace ad applicatios that wat to iteract with databases o a SQL server. Whe a alias is defied o a machie, you must specify a miimum of two parameters: a server ame ad a alias ame. Oce you have established such a alias, coectio strigs that would ormally use the server ame ca istead use the alias ame. If the server ame eeds to be chaged or updated, updatig the alias is all that is required. The use of aliases affords a great deal of flexibility ad portability for SharePoit farms ad applicatios that leverage them. Mapped etwork drives. Mapped etwork drives are a commo approach to idetifyig etwork resources usig local path specificatios. Nearly all applicatios ad platforms support the otio of mapped drives i some sese, makig them a solid backwardcompatible approach to separatig idetifier from implemetatio. Ufortuately, mapped drives ted to be established o a per-user or per-sessio basis. This limits their potetial usefuless i may cases, particularly regardig activities that are carried out withi the cotext of a oiteractive accout. The oly methods that should be avoided wholesale whe accessig etwork resources are those ivolvig direct IP address access ad the use of NetBIOS or straight machie ames. Both of these methods fail to leverage a abstractio layer of some sort, so their viable use withi a fuctioal disaster recovery eviromet is questioable. After all, most live data ceters (or failover targets) have servers ad amig schemes that differ from those beig used i the stadard productio eviromets that are beig protected by the disaster recovery implemetatio. Whe it comes to custom SharePoit applicatios, developers are advised to simply use DNS wheever possible if calls to other sites or etwork resources are required. SharePoit s alterate access mappig (AAM) capability simplifies the process of extedig ay SharePoit site that may have a IP address i its URL to make it addressable by DNS ame, so SharePoit is exceptioally DNS friedly for applicatios attemptig to access its sites ad Web services. Because SharePoit s AAM capabilities ad zoe mappigs are also accessible through the SharePoit

389 372 SharePoit 2010 Disaster Recovery Guide object model (usig the SPWebApplicatio.AlterateUrls property, for istace), it s easy to esure that custom SharePoit applicatios ca cope with evirometal chages ad gracefully fall back to alterate access poits to a site if eeded. Applicatio Loggig ad Moitorig The previous desig readiess suggestios focused primarily o ways to decouple addressig ad usage of applicatio resources ad data. The fial recommedatios offered i this sectio focus o providig isight ad uderstadig ito how a applicatio is operatig. Loggig ad moitorig are fairly commo applicatio requiremets, but these areas are ofte iadequately addressed or supported whe developmet is udertake. May times, they are see as a ice to have, rather tha a critical facet of a fully fuctioal ad well-architected applicatio. I a disaster recovery sceario, loggig ad moitorig take o additioal importace. This is especially true whe a custom applicatio may have a recovery time objective (RTO) that is measured i hours or maybe eve miutes. You simply do t have the luxury of takig ay measurable amout of time i such circumstaces to focus o troubleshootig a problematic applicatio. If a applicatio has issues comig olie whe recovered, the reasos for those issues eed to be clearly spelled out. At a miimum, applicatios should commuicate ot oly errors, but critical iformatioal items regardig where data is beig accessed ad utilized, security checks that pass ad fail, aytime a applicatio is fallig back to a default value, ad so o. A commo mechaism for the commuicatio of this iformatio is the Widows Evet Log, but items that are more iformatioal i ature are ofte better supported ad cotrolled through the use of trace switches ad flags. Beig built upo ASP.NET, SharePoit has access to ASP.NET s full array of evet tracig ad otificatio capabilities. Errors, warigs, ad other iformatioal items ca be writte to the ASP.NET trace logs ad evet siks. Critical applicatio errors ca be added to the AllErrors collectio of the SPHttpCotext for further processig ad aalysis dowstream i the ASP. NET pipelie. I additio to these capabilities, SharePoit has its ow uified loggig service (ULS) to which developers ca write messages of ay sort. SharePoit 2010 also itroduces correlatio IDs for troubleshootig ad the loggig database for aggregatig iformatio from across a farm. These capabilities greatly simplify the problem of pipoitig issues that arise with custom SharePoit code ad applicatios. Icludig Widows performace couters is aother step forward that ca promote greater supportability ad troubleshootig with missio-critical applicatios. This is particularly true for applicatios that operate as services or lack ay form of iterface. Thoughtfully chose ad implemeted couters ca mea the differece betwee befuddled head scratchig ad isight whe attemptig to idetify the source of a problem durig recovery.

390 Chapter 11 SharePoit 2010 Disaster Recovery Developmet 373 Both SharePoit ad ASP.NET come with a variety of performace couters that you ca leverage out of the box to troubleshoot applicatio ad performace problems. I additio, developers have the stadard abilities offered by.net to create performace couters of their ow for their SharePoit applicatios. Coclusio Although SharePoit disaster recovery operatios are typically the provice of farm admiistrators ad operatios persoel, kowledge of the ways i which you might customize, exted, ad automate the SharePoit platform ca prove useful. Possessio of some custom developmet ad PowerShell kowledge ca help you avoid repetitive tasks that commoly lead to errors, permit the developmet of tailored solutios that solve ovel or busiess-specific techology problems, ad geerally save coutless hours ad may headaches i the log ru. Whe the SharePoit platform lacks the facilities to adequately address disaster recovery eeds, custom developmet usig the SharePoit API ca be used i situatios ad scearios that are either iappropriate or simply too complex for PowerShell scriptig aloe. SharePoit makes a umber of optios available for custom backup ad restore operatios, icludig the catastrophic backup ad restore types of the Microsoft.SharePoit.Admiistratio. Backup amespace ad the relatively self-cotaied SPSiteCollectio type. SharePoit also offers a Cotet Deploymet API that is exposed through the Microsoft.SharePoit. Deploymet amespace. You ca leverage the types foud withi to exted export ad import operatios. I additio to the built-i types metioed, you are free to craft your ow solutios for cotet protectio, backup, ad restoratio. Maaged code implemetatios may ceter o object model walkig with some type of custom persistece or serializatio scheme. Eterprise-ready idustrial solutios, o the other had, ofte ivolve the use of VSS i cojuctio with the SharePoit Foudatio VSS Writer to achieve backup cosistecy ad scalability. Fially, you should factor a umber of techiques ad cosideratios ito the desig of ay applicatio that is a cadidate for locatio ad operatio i multiple eviromets, because this ofte happes i a disaster recovery sceario whe multiple data ceters ad workstatio eviromets are i play. Certai practices such as idirect access to etwork resources, clear segregatio betwee applicatios ad their associated cofiguratio data ad busiess data, ad the cetralizatio of busiess data ca sigificatly aid i the recoverability of a applicatio ad greatly reduce dowtime i the evet of a disaster. Architectig applicatios to adequately support loggig ad performace moitorig ca also greatly improve troubleshootig efforts whe a applicatio does ecouter problems i both disaster ad odisaster scearios. Havig completed this chapter, you should ow be able to aswer the followig questios. As with the other chapters, aswers to the followig questios appear i Appedix A, Chapter

391 374 SharePoit 2010 Disaster Recovery Guide Review Q&A, foud o the Cegage Learig Web site at dowloads. 1. Through what object are all operatios ivolvig farm-level catastrophic backup ad restore operatios coducted? 2. If you ited to tap ito the catastrophic backup ad restore object model, what two iterfaces do you eed to be aware of? How do they differ? 3. How do backups performed through the SPSiteCollectio type differ from stadard farm-level backups? 4. True or false: The Cotet Deploymet API is leveraged by both the Backup-SPFarm ad Export-SPWeb PowerShell cmdlets? 5. What is the differece betwee a VSS writer ad a VSS requestor?

392 12 SharePoit 2010 Disaster Recovery for Ed Users I This Chapter What Has Chaged i SharePoit 2010 Recycle Bis Versioig Templates WebDAV ad Explorer View SharePoit Workspace 2010 Amidst the discussios surroudig SharePoit disaster recovery, server redudacy, data backups, ad related areas, it is easy to overlook the majority stakeholders i your activities: the ed users. Ed users typically create the data you wat to protect. They ofte do t have ay real familiarity with the techical aspects of disaster recovery, ad they typically rely o you for recovery of their data ad restoratio of system fuctioality i the evet of a disaster. The depedece that ed users have o iformatio techology (IT) persoel like you ca be a source of axiety for them, ad it is t hard to uderstad why. No oe likes to feel as if they possess little or o cotrol over their ow fate or the fate of their data. To may admiistrators, a ed user s data is just a abstract etity that has to be protected by a disaster recovery pla. A ed user s relatioship with his data is typically much more persoal. To a ed user, his data ca be the result of coutless hours worth of research, pictures that ca ever be replaced, or documets that he is legally boud to store ad produce o-demad for years. Ed users do t forfeit all rights to their data whe they place it i SharePoit, or do they require blid faith i a admiistrator s ability to brig thigs back whe eve mior outages limit SharePoit access. SharePoit icludes features that give some cotrol back to cotet authors ad owers. This chapter discusses disaster recovery related optios that average ed users ca leverage to safeguard their data ad recover from mior losses. It also covers the aspects of those optios that you, the admiistrator, eed to be familiar with. 375

393 376 SharePoit 2010 Disaster Recovery Guide What Has Chaged i SharePoit 2010 If you are familiar with the data protectio ad recovery optios that were available to ed users i SharePoit 2007, you already kow most of the optios that SharePoit 2010 brigs to the table. The form ad presetatio of some features have chaged a bit, but items like Recycle Bis ad the creatio of site templates are still very much a part of SharePoit Not everythig remais the same, however. Microsoft decided to chage the playig field i 2010 by alterig the operatio of two importat applicatios: Microsoft SharePoit Workspace Whe movig from Office 2007 to Office 2010, Microsoft chose to overhaul ad rebrad Microsoft Office Groove 2007 as Microsoft SharePoit Workspace 2010 (also kow simply as SharePoit Workspace). SharePoit Workspace is a rich cliet applicatio that builds o capabilities that existed i Groove 2007 ad provides ed users with a variety of optios for workig with SharePoit data i offlie ad multiuser cocurret editig scearios. Because SharePoit sites ad data cotaied withi them ca be take offlie ad sychroized betwee cliet systems ad the Share- Poit server eviromet, a umber of data replicatio ad protectio optios have arise that were previously difficult or impossible to achieve. Microsoft SharePoit Desiger SharePoit Desiger also received a overhaul i the move from 2007 to 2010, but it became sigificatly less fuctioal with regard to Share- Poit data protectio. Although SharePoit Desiger 2010 retais its ability to lik to a SharePoit site for the purpose of creatig site ad list templates, it loses both its Web site backup ad its persoal Web package export capabilities. The loss of these two capabilities meas that SharePoit Desiger o loger offers ay additioal form of data protectio to ed users beyod what is offered by the browser-based user iterface (UI) itself. A Word o Ed Users ad Disaster Recovery Let s cut to the chase: whe the chips are dow ad you are formulatig a disaster recovery strategy for your SharePoit eviromet, the tools ad techiques that are discussed i this chapter are t goig to play a sigificat part i the pla you assemble. At best, they may play a small role i some of your outage mitigatio plas, but they simply are t eterpriseready or desiged for use i true disaster recovery scearios. That does t make the cotets of this chapter irrelevat to the overall disaster recovery picture, however. As was metioed earlier, the SharePoit ed user populatio is commoly overlooked whe admiistrators assemble their plas to keep servers ruig ad recover from eterpriselevel outages. Ed users ca idepedetly employ may of the tools ad techiques that are described i this chapter to cotiue operatig durig mior outages ad recover data i limited scearios.

394 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 377 Although this chapter discusses cocepts ad capabilities that are ultimately of iterest primarily to ed users, there is a admiistrative perspective o these cocepts ad capabilities that is of iterest to you. We structured this chapter to give you a basic explaatio of each tool or techique that ed users may employ; that explaatio is the followed with the poits that you, the admiistrator, eed to uderstad ad itegrate to effectively maage ad support the associated tool or techique i your eviromet. We placed emphasis o exposig cotrol poits ad settigs that you ca employ to safeguard your SharePoit eviromet agaist iappropriate storage cosumptio, slowdow of the user experiece, ad other adverse operatioal effects that might be brought o by excessive use or misuse of the ed user capabilities described withi. So eve if the cotets of this chapter do t help you directly i all cases, a solid uderstadig ad careful applicatio of the cocepts withi may allow your ed users to cotiue workig whe they otherwise might ot be able to. A ed user who is still workig is a ed user who is t callig you, the admiistrator, for data recovery or support help. Tryig It Out The screeshots ad examples i this chapter were put together i a virtual eviromet with the followig software ad cofiguratio. Depedig o how your eviromet is cofigured, your experieces may vary slightly. Operatig system. Microsoft Widows Server 2008 R2 Eterprise Editio (build 7600) Database. Microsoft SQL Server 2008 R2 Eterprise Editio (build ) Web server. Microsoft Iteret Iformatio Services (IIS) 7.5 Cliet Web browser. Iteret Explorer 8 (versio ) SharePoit. SharePoit Server 2010 RTM with Eterprise Cliet Access Licese (build 4763) Recycle Bis SharePoit 2007 brought itegrated Recycle Bis to the platform, ad they remai i SharePoit 2010 as a corerstoe of the ed user self-service recovery ladscape. How They Work If you have worked with ay versio of the Widows operatig system sice Widows 95, you are probably well acquaited with the cocept of a Recycle Bi ad its operatio. Whe cotet is deleted from the file system i Widows, it is t immediately deleted from the hard drive or local media where it is located if a Recycle Bi is active for that locatio. Istead, the deleted cotet is moved from where it resides to a special system folder. Recycle bis address the ed user problem of uitetioally ad accidetally deleted cotet. If cotet is accidetally deleted from the Widows file system, you ca recover it from the Recycle Bi ad put it back ito geeral availability withi the file system. Deleted cotet sits i the Recycle Bi util it is either recovered or deleted (emptied) from the Recycle Bi.

395 378 SharePoit 2010 Disaster Recovery Guide Cotet that is emptied from the Recycle Bi is permaetly deleted. Third-party tools exist that ca help with the recovery of cotet that is permaetly deleted from the Widows file system, but o mechaism is built ito the operatig system to assist i this regard. Recyclig i SharePoit SharePoit s Recycle Bi system is coceptually similar to the Recycle Bi that the Widows operatig system employs, but there are a hadful of oteworthy differeces ad poits worth discussig: SharePoit Recycle Bis are cofigured at the Web applicatio level. You ca cofigure Recycle Bi settigs for each Web applicatio i your SharePoit farm through the Web Applicatio Geeral Settigs dialog box i the Cetral Admiistratio site, as show i Figure By default, each ewly created Web applicatio is provisioed with the settigs show i Figure 12.1, ad these settigs apply to all site collectios that are created withi the Web applicatio. Figure 12.1 Recycle Bi settigs for a Web applicatio. The SharePoit Recycle Bi has two cofigurable stages. As show i Figure 12.1, SharePoit s Recycle Bi system actually has two separate stages. Whe a user deletes a item, a documet, or some other cotet from a site collectio, the deleted item is moved ito the first stage Recycle Bi. The first stage Recycle Bi is a area from which ed users ca recover their ow documets; it is basically the equivalet of their ow persoal Recycle Bi. If a user the deletes a item from the first stage Recycle Bi, the item is actually moved from the first stage Recycle Bi to the secod stage Recycle Bi. Oly site collectio admiistrators ca recover items from the secod stage Recycle Bi. Whe items have bee deleted from the secod stage Recycle Bi, they are permaetly deleted. By default, both the first ad secod stage Recycle Bis are eabled i a Web applicatio, so site collectios created i the Web applicatio have first ad secod stage Recycle Bis available to them.

396 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 379 Recycle Bi cotets ca be auto-expired. Items i the first ad secod stage Recycle Bi areas have a lifetime of 30 days by default. After 30 days, these items are permaetly deleted regardless of their Recycle Bi stage. This meas that items i the first stage of the Bi are permaetly deleted, as well; there is o promotio or movemet of items from the first to the secod stage of the Recycle Bi after the expiratio period has elapsed, for example. You ca adjust the auto-deletio period for items or tur it off etirely for site collectios i a Web applicatio usig the Web Applicatio Geeral Settigs dialog box. The size of the Recycle Bi is cofigurable. To be more specific, the amout of storage available to the secod stage Recycle Bi is cofigurable. There is o separate storage set aside for items i the first stage Recycle Bi; items cout agaist ay maximum storage quota that has bee established for a site collectio. The secod stage Recycle Bi, o the other had, is allotted a additioal amout of storage that is equal to 50 percet of the amout allotted to the site collectio by the quota template that is i effect. You ca adjust this percetage from 1 percet all the way up to 500 percet. There are o size restrictios o a site collectio s first ad secod stage Recycle Bis if o quota template is i effect for the site collectio. Cofigurig Recycle Bis By default, both Recycle Bi stages are eabled for ew site collectios that are created i a Web applicatio that utilizes the default Recycle Bi settigs. This meas that ed users automatically gai Recycle Bi protectio for their site collectios, but the Web applicatio defaults do t iclude safeguards to prevet ucotrolled site collectio growth. Applyig reasoable limits for Recycle Bi usage ad site collectio growth is relatively easy to do if you have Farm Admiistrator access withi the Cetral Admiistratio site. First, you must create a quota template for assigmet to the target Web applicatio. The quota template the becomes the basis for the limits that are placed o the size of the first ad secod stage Recycle Bis o ewly created site collectios withi the Web applicatio. Secod, you must cofigure the target Web applicatio to use the quota template by default for ew site collectios whe they are created. While the quota template is beig assiged, the Web applicatio settigs are also adjusted to set desirable Recycle Bi limits for site collectios created withi the Web applicatio based o values that are specified i the quota template. Creatig a Web Applicatio Quota Template The example that follows demostrates how to use Cetral Admiistratio to create a ew quota template called 500MB Maximum Template that restricts site collectios that use the template to o more tha 500MB, as suggested by its ame. You ca the use the quota template i the ext walk-through titled Cofigurig a Web Applicatio s Recycle Bi Settigs. Before attemptig this walk-through, esure that you are a member of the SharePoit Farm Admiistrators group. I additio, make sure that you are logged ito a computer that ca

397 380 SharePoit 2010 Disaster Recovery Guide access the SharePoit Cetral Admiistratio site. This is ofte your ow workstatio, but i some highly secure eviromets, access to the Cetral Admiistratio site may be restricted to oly a select group of servers ad workstatios. 1. Ope a browser ad avigate to the Cetral Admiistratio site. This example uses a fictitious SharePoit 2010 Server farm with a Cetral Admiistratio site URL of spdev: If you ited to follow alog i your ow eviromet, simply substitute your farm s Cetral Admiistratio site URL where appropriate. 2. Depedig o the cofiguratio of both the SharePoit farm ad your cliet browser, you may be prompted to log ito the Cetral Admiistratio site. If you are so prompted, supply both your userame ad password. I most cases, your userame ad password are your domai logi credetials. 3. Whe the Cetral Admiistratio site loads, avigate to the Applicatio Maagemet page, as show i Figure You do this by clickig the Applicatio Maagemet lik i the Quick Lauch meu alog the left side of the page. Alteratively, you ca click the Applicatio Maagemet lik i the top-left regio of the mai zoe o the page. Figure 12.2 The Applicatio Maagemet page i Cetral Admiistratio. 4. Click the Specify Quota Templates lik. It is the fourth lik uder the Site Collectios sectio i the mai zoe of the page, ad it takes you to the Quota Templates page. 5. Select the optio butto to Create a New Quota Template, ad leave the startig template default value itact so the quota template is t based o aother quota template. I the New Template Name text box, eter 500MB Maximum Template.

398 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users I the Limit Site Storage to a Maximum Of text box, supply a value of 500. This prevets ew site collectios that are created i a Web applicatio usig the quota template from growig beyod 500MB. Esure that the check box associated with the text box remais checked. 7. I the Sed Warig Whe Site Collectio Storage Reaches text box, supply a value of 450 ad esure that the associated check box remais checked. If the site collectio grows to 450MB or greater, a is set to the primary ad secodary (if specified) site collectio admiistrators for the site collectio warig that the storage threshold has bee crossed. 8. Leave the Sadboxed Solutios with Code Limits cotrols itact with their default values. Note: If you ited to execute sadboxed solutios i oe or more of the site collectios associated with the Web applicatio that a quota template will be applied to, you must specify usage limit poit values that are greater tha the defaults of zero; however, the use ad cofiguratio of sadboxed solutios is beyod the scope of this book. 9. Whe you have executed these steps, the settigs for the ew quota template to be created should appear as i Figure To actually create the quota template, scroll to the bottom of the page ad click the OK butto. Figure 12.3 The ew 500MB Maximum Template quota template.

399 382 SharePoit 2010 Disaster Recovery Guide Cofigurig a Web Applicatio s Recycle Bi Settigs With a quota template i had, you are ready to cofigure the Web applicatio of your choice. I this example, a fictitious Web applicatio with a URL of is cofigured to use the 500MB Maximum Template quota as the default quota template for ew site collectios that are created withi it. The assigmet of the quota template permits limits to be set o the amout of storage cosumed by ew site collectios that are created withi the Web applicatio. A reductio i the size of the secod stage Recycle Bi to a limit of 100MB per ew site collectio is also carried out i this example. Before attemptig this walk-through, esure that you are a member of the SharePoit Farm Admiistrators group. I additio, make sure that you are logged ito a computer that ca access the SharePoit Cetral Admiistratio site. This is ofte your ow workstatio, but i some highly secure eviromets, access to the Cetral Admiistratio site may be restricted to oly a select group of servers ad workstatios. 1. Repeat steps 1 through 3 i the previous walk-through to arrive at the Applicatio Maagemet page i the Cetral Admiistratio site. 2. Click the Maage Web Applicatios lik. It is the first lik uder the Web Applicatios sectio i the mai zoe of the page, ad it takes you to the Web Applicatios Maagemet page. 3. If you are ew to the Fluet UI, also kow as the ribbo, Figure 12.4 may ot be familiar to you. May of the fuctios that are performed o Web applicatios are performed through the ribbo oce a Web applicatio has bee selected. The first step i workig with the ribbo is esurig that it is visible. If you do t see the ribbo as show i Figure 12.4, you probably have the Browse tab selected. Click the Web Applicatios tab that is circled i Figure 12.4 to make the ribbo visible. Figure 12.4 Clickig the Web Applicatios tab to make the ribbo visible.

400 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users The Web applicatio of iterest i this example is the PublishigTestWeb Web applicatio with a URL of To select the Web applicatio, click o the Web applicatio lik show i Figure Oce you have selected the Web applicatio, the liks ad meus i the ribbo shift from grayed-out ad iactive to live ad available. Figure 12.5 Selectig the target Web applicatio. 5. Expad the Geeral Settigs drop-dow meu i the ribbo, as show i Figure 12.6, ad select the Geeral Settigs meu item. Doig so opes the Web Applicatio Geeral Settigs dialog box pictured i Figure Figure 12.6 The Web applicatio Geeral Settigs drop-dow meu.

401 384 SharePoit 2010 Disaster Recovery Guide Figure 12.7 The Web Applicatio Geeral Settigs dialog box freshly opeed. 6. The Select Quota Template drop-dow selectio box appears i the Default Quota Template sectio, ad by default it is set to No Quota. If the last walk-through was completed successfully, the 500MB Maximum Template should appear i the list of available quota templates, as show i Figure Select it so that ew site collectios that are created withi the Web applicatio are costraied to o more tha 500MB by default. Figure 12.8 Selectig the 500MB Maximum Template. 7. Scroll dow to the Recycle Bi sectio, as show earlier i Figure Items that are placed i the first stage Recycle Bi cout agaist the maximum storage of 500MB per site collectio, but this is ot true of the secod stage Recycle Bi. The 50 percet additioal storage allocatio meas that deleted items that ed up i the secod stage (site collectio) Recycle Bi could cosume up to a additioal 250MB of storage. To tighte up the amout of extra space that might be cosumed, chage the Percet of

402 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 385 Live Site Quota for Secod Stage Deleted Items value from 50 to 20. Oce you make this chage, items i the secod stage Recycle Bi are the oly able to cosume up to a additioal 100MB of storage (that is, 20 percet of 500MB) o top of the 500MB already allocated per ew site collectio i the Web applicatio. 8. Scroll dow to the bottom of the Web Applicatio Geeral Settigs dialog box ad click the OK butto to apply the chages made. Note: If you have bee readig carefully, you have probably oticed that quota-related chages to a Web applicatio affect oly ew site collectios that are created withi the Web applicatio after a quota template has bee assiged. At the same time, it is possible to override the default quota template specified for a Web applicatio durig the site collectio creatio process. This meas that idividual site collectios withi a Web applicatio may possess a variety of differet quota settigs. If you later wat to chage the quota settigs that are applied to a existig site collectio, you eed to use the Cofigure Quotas ad Locks lik o the Applicatio Maagemet page or the Set-SPSite Power- Shell cmdlet with its QuotaTemplate parameter. The Site Collectio Quotas ad Locks page that appears provides the mechaism you eed to alter the quota ad alert settigs o existig site collectios. With PowerShell ad Set-SPSite, you ca script out a process to update the quota template for multiple site collectios i oe fell swoop. Versioig Versioig is aother SharePoit feature that is relatively easy to grasp. Simply put, versioig is a feature that allows you to store multiple revisios or copies of a particular item withi a documet library or list. A example ca illustrate how exceptioally useful this is for ed users. Cosider the fictitious example of several authors workig to assemble a book. Those authors decide to use a SharePoit documet library as a repository for the storage of the chapters they are writig. The book is a collaborative effort, so each of the authors is expected to cotribute somethig to each chapter. I this type of editig sceario, it s importat to track the state ad cotets of the chapters as they are edited by each author i tur. At the same time, it s occasioally desirable to go back to a previous revisio of the chapter to see how it existed before some chages were made. Versioig ca satisfy these eeds ad more. Types of Versioig Versioig is a cetral feature of the SharePoit platform that you ca use with ay documet library or list. Versioig is eabled for some of the out-of-the-box documet libraries, such as the Pages library that is created i the top-level site where the SharePoit Server Publishig Ifrastructure is active. With most documet libraries ad lists, though, you must explicitly eable versioig.

403 386 SharePoit 2010 Disaster Recovery Guide Although versioig has bee used as a sigular term thus far, versioig actually exists i two differet forms withi SharePoit: Major versioig. This type of versioig is available for use o both documet libraries ad lists. Each time a item i a list or documet library is edited, updated, or chaged i some way, a ew versio of that item is created whe it is put back ito the list or documet library. Versio umbers begi at 1 ad icremet by 1 for each ew versio that is stored i the list or documet library. The iitial versio of a item is versio 1, the secod is versio 2, the third is versio 3, ad so o. Major ad mior (draft) versioig. This type of versioig is available oly o documet libraries ad other libraries based o them, such as Picture Libraries. It is ot available o lists. This type of versioig exteds the major versioig approach just described with the additio of draft versios that are deoted by a poit versio umber. For example, a documet may be iitially uploaded ito a documet library as versio 1.0. As chages are made to the documet, drafts of the documet may accumulate as mior versios: 1.1, 1.2, 1.3, ad so o. Oce the revisio process is complete ad aother versio is ready for geeral viewig or usage, the versio umber is icremeted to 2.0. Major versio umbers (1.0, 2.0, ad so o) deote published versios, whereas mior versios (1.1, 1.2, 2.1, ad so o) deote mior or draft versios. Versioig Beefits Figure 12.9 illustrates a documet library for which major ad mior versioig is active. I the figure, the meu selectios for Chapter 11, SharePoit 2010 Disaster Recovery Developmet, are displayed. Selectig the Versio History meu item from the drop-dow selectio meu opes the Versio History dialog box show i Figure Figure 12.9 A item s drop-dow meu i a documet library where versioig is eabled.

404 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 387 Figure The Versio History dialog box for a selected documet library item. Several beefits are afforded by versioig regardless of the type of versioig that is i use or whether versioig is eabled o a list or library: Versio history. The Versio History dialog box is the primary poit of iteractio whe viewig ad workig with item versios. Each time a item is chaged, a ew versio is created. As demostrated i Figure 12.10, each of the versios that are available for a give documet or list item is clearly show. Auditig ad chage trackig. Alog with the versio umbers, the Versio History dialog box makes it clear whe a item was modified ad by whom. The size of the item is also oted, alog with ay commets that were supplied by the idividual creatig the versio. As log as good commets were supplied whe the versio was created, it ca be a sap to locate a versio or revisio of iterest. Maagemet of versios. The Versio History dialog box also affords you the meas to maage the curret item versio ad those that are historical, either idividually or as a group. As show i the ope drop-dow meu for versio 1.2 i Figure 12.10, you ca view the item as it existed i versio 1.2 or delete that versio of the item altogether. You ca also replace the curret versio (2.0, i this case) with a historical versio, although the term replace is a bit iaccurate. If you elected to replace versio 2.0 with the selected versio (1.2) show i Figure 12.10, a versio 2.1 would be created with the cotets of versio 1.2. Versio 2.0 would ot actually be replaced or overwritte. Figure illustrates the results of such a replacemet operatio.

405 388 SharePoit 2010 Disaster Recovery Guide Figure Replacemet of the curret item versio with a previous versio. From a ed user disaster recovery perspective, the biggest beefit that versioig gives users is the ability to roll back to a previous versio of a documet if the curret versio icludes chages or differeces that are t desired. Whe a user ca roll back to a previous documet or item versio, it is oe less call that he s placig to you for a item-level recovery. Admiistrative Cocers Versioig is cotrolled o a per-list/library basis. Because lists ad libraries are maaged withi the cofies of a site collectio, there is t a whole lot that you, as a SharePoit admiistrator, eed to worry about i terms of farm-wide impact as log as you employ site collectio quotas to limit the cosumptio of cotet database storage. As you might imagie, though, the use of versioig does icrease storage cosumptio. Each time a ew major or mior item versio is added to a list or library, aother copy of that item is created. Take the Versio History for the Chapter 11 SharePoit DR Developmet list item show earlier i Figure A total of six versios for the documet exist: 1.0, 1.1, 1.2, 1.3, 2.0, ad 2.1. Each of the versios cosumes roughly 185KB, so eve though the active 2.1 versio is oly 184KB i size, the total storage space cosumed by all versios is more tha 1MB. For lists ad libraries i which collaboratio activities are used heavily, the overhead of multiple versios ca quickly add up, cosume storage, ad push a site collectio size toward its allocatio limit o storage space as defied by its quota. Fortuately, SharePoit provides a maximum umber of versios retaied mechaism that provides some degree of cotrol over the extet to which item ad documet versios may impact your overall site collectio storage profile.

406 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 389 Cofigurig Versioig The example that follows demostrates how to eable versioig o a documet library called Book Chapters at the root of a fictitious SharePoit team site with a URL of I additio to eablig versioig, the maximum umber of versios that ca be stored for each documet i the library are specified. If you attempt this walk-through o a SharePoit site of your ow, esure that your accout possesses a miimum permissio level of Cotribute withi the site housig the documet library. 1. Ope a browser ad avigate to the site s URL of If you ited to follow alog i your ow eviromet, substitute this URL with the URL of a team site i your eviromet. 2. Depedig o the cofiguratio of your cliet browser ad the Web applicatio housig the site, you may be prompted to log i. If you are so prompted, supply both your userame ad password. I most cases, your userame ad password are your domai logi credetials. 3. Whe the team site loads, you are greeted with the default page. Uder the Libraries headig i the quick lauch meu alog the left side of the scree is a Book Chapters lik. Click the lik to take you to the Book Chapters documet library show i Figure Figure The Book Chapters documet library i a sample team site.

407 390 SharePoit 2010 Disaster Recovery Guide 4. By default, the Browse tab is selected ear the top of the documet library. Before you ca begi cofiguratio, click the Library tab uder the Library Tools groupig. This displays the Documets Library Settigs ribbo show i Figure Figure The ribbo for Documets Library Settigs. 5. The actual cotets of the ribbo ad how they are preseted deped o the width of your browser widow. The lik of iterest o the ribbo is ear the right side, though, ad it is called Library Settigs. Whe you have located it, click the lik to brig up the Documet Library Settigs page for the library. 6. Uder the Geeral Settigs category alog the left side of the mai area is a lik titled Versioig Settigs. Click the lik to display the Versioig Settigs page show i Figure Figure The Versioig Settigs page for a documet library.

408 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users By default, the Documet Versio History idicates that No Versioig is i use. To begi usig versioig withi the documet library, select either Create Major Versios or Create Major ad Mior (Draft) Versios. The latter teds to be the more useful form of versioig whe trackig documets, so select it. 8. Oce you select the Create Major ad Mior (Draft) Versios optio butto, the versio retetio check boxes ad text boxes just below it become active. The check boxes ad text boxes provide a way to cotrol the total umber of retaied versios. Set the first check box ad text box for major versio retetio to appear, as show i Figure With these values i effect, te major versios (1.0, 2.0, ad so o) are available at ay give time. Oce versio 11.0 is placed ito the documet library, versio 1.0 is dropped from the available versio history. Whe versio 12.0 is placed ito the documet library, versio 2.0 is dropped. This patter repeats to esure that oly te major versios are available at ay give time. Figure Specifyig major versio ad draft retetio settigs. 9. Set the secod check box ad text box, as show i Figure Specifyig that three major versios worth of drafts are retaied results i all drafts other tha those belogig to the curret major versio ad the two previous oes beig discarded. If the most recet major versio is 8.0, for example, oly the draft (poit) versios for versios 6.0, 7.0, ad 8.0 are available. Ay drafts that existed for previous versios (such as 5.1 ad 5.2) are discarded. Whe versio 9.0 is made available, all existig drafts for versio 6.0 are dropped with these settigs. Whe versio 10.0 is made available, drafts for versio 7.0 are dropped. You get the idea. 10. Scroll to the bottom of the Versioig Settigs page ad click the OK butto to place your chages ito effect. As a admiistrator, you should be happy to hear that Recycle Bis ad versioig work together ad complemet oe aother quite well. Whe a list item is deleted from a documet library or list, the versio history for the item goes with it to the Recycle Bi. By the same toke, recoverig a item from either the first or secod stage Recycle Bis also restores that list item s versio history.

409 392 SharePoit 2010 Disaster Recovery Guide Templates Customizatio of SharePoit sites through the UI is a labor of love for some. For others, it s simply work. Regardless of how or why it is doe, customizatio is somethig that ed users ca sped coutless hours doig i SharePoit. Customizatio activities iclude alterig the look ad feel of a site, creatig custom views for lists, modifyig the usage ad settigs for Web parts, ad much more. Note: I the cotext of this sectio, the term customizatio is beig used to describe chages that ed users make to a SharePoit site or its costituet parts through the browser-based UI or SharePoit Desiger. Customizatio does ot refer to farm-deployed solutios, sadboxed solutios, or ay other form of code-based solutio uless explicitly idicated. Oe way that ed users ca capture ad save such customizatios withi the SharePoit eviromet is through the use of templates. For example, a template ca be used to budle up the chages that are made to a list, modificatios that have bee made to the colums it cotais, views that have bee added or chaged, ad more. I additio to capturig these structural chages, templates ca be used to save data ad cotet. I the case of the list example, ed users have the optio of choosig to iclude the data that is i a list at the same time the structural iformatio is captured i a template. Oce you have created a template, it is available for re-use withi the site collectio it was created withi. Ed users ca also dowload templates that have bee created for use i other site collectios ad SharePoit eviromets; this use is most attractive to the average ed user from a cotet protectio ad disaster recovery perspective. With the removal of persoal Web package export ad backup creatio capabilities from Share- Poit Desiger 2010, templates remai oe of the few mechaisms that ed users have at their disposal to package ad move cotet out of SharePoit sites i a structured form. Templates that ca be created, exported, ad imported by users come i two varieties: list templates ad site templates. List Templates The first type of template that ed users ca geerate through the SharePoit browser-based UI is a list template. The overwhelmig majority of data ad cotet withi SharePoit is stored i list form, so the ability to create a reusable template from virtually ay list i SharePoit is quite powerful. As described earlier, a list template allows ed users to capture the structure ad customizatios that are tied to a specific list or documet library i SharePoit. At the same time, ed users ca choose to iclude all the list item cotet that the list or documet library possesses at the time of template creatio.

410 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 393 The process of list template creatio ca be distilled ito the followig sequece of steps: 1. Customize a list or documet library ad optioally load it with cotet i the form of list items. 2. Select the Save... as Template lik from withi the settigs page for the list or documet library i the browser-based UI. 3. O the Save As Template Web page that is displayed, provide a file ame, template ame, ad descriptio. Optioally, you ca specify that list or documet library cotet be icluded with the template. 4. SharePoit adds a ew list item to the List Template Gallery for the site collectio cotaiig the list or documet library that was used to geerate the template. Templates that are preset i the List Template Gallery as a result of the steps just described are available for ed users to select whe they go to create a ew list or documet library i the site collectio. You ca also dowload templates i the List Template Gallery with the Save Target As optio that is available whe you right-click a template ame, as show i Figure Figure Savig a template from the List Template Gallery. Templates that you dowload ca be imported ito aother site collectio usig the Upload Documet optio o the ribbo of the List Template Gallery. Oce you have uploaded a list template to the List Template Gallery, it becomes available for use i the creatio of ew lists i the destiatio site collectio just as it had bee i the source site collectio.

411 394 SharePoit 2010 Disaster Recovery Guide Site Templates The secod type of template that ca be geerated from withi the browser-based UI is a site template. Whereas you use a list template to capture the structure ad cotet of a sigle list or documet library, you use a site template to capture the equivalet iformatio for a etire SharePoit site or subsite. The template process does t recursively capture subsites below the site targeted, though oly the site itself. I most regards, the process of creatig ad usig a site template is the same as the process that was described for list templates. There are a few differeces worth otig, though. The lik to create a template is located uder the Site Actios meu of the Site Settigs page. Templates that you create are stored (somewhat oituitively) i the Solutios Gallery for the site collectio. You ca dowload existig templates from the Solutios Gallery, ad you ca upload templates that you wat to import to the Solutios Gallery. Templates i the Solutios Gallery are available for selectio whe ed users wat to create a ew site or subsite, such as through the New Site optios o the Site Actios meu. SharePoit Desiger ad Templates If you have used SharePoit Desiger 2010 ad examied the applicatio s ribbo while workig with either a site or list, you have probably see the Save As Template butto that is show circled i Figure Figure SharePoit Desiger s Save As Template ribbo butto. As was the case with SharePoit Desiger 2007, this butto does t lauch applicatio-specific fuctioality withi SharePoit Desiger Istead, it opes a browser widow ad directs the browser to the savetmpl.aspx applicatio page i SharePoit s _layouts virtual directory. From the savetmpl.aspx page, you have the ability to create both site ad list templates. That s the extet to which SharePoit Desiger assists with site ad list template creatio. Iterestigly eough, the savetmpl.aspx page is the same page from which site ad list templates are created whe usig the browser-based UI for these tasks. I reality, SharePoit Desiger does t really provide template creatio capabilities it simply hads cotrol over to a SharePoit applicatio page ad removes itself from the operatio.

412 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 395 A Admiistrative Perspective o Templates Much like versioig, the creatio ad use of both site ad list templates are tasks that ed users ca carry out o their ow without havig to trouble you, the admiistrator. There are a few template-related poits of ote, though, that you should be aware of. Templates ad Publishig Sites Whe your users begi workig with templates, they may report that the liks to create site ad list templates do t always appear withi the Site Settigs ad List Settigs pages. I additio, your users may report that the Template Creatio butto o the ribbo i SharePoit Desiger is sometimes grayed out. I most cases, this behavior is by desig ad is tied to site collectios that are based o publishig templates such as the Publishig Portal ad Eterprise Wiki. Due to some of the uique relatioships that exist withi publishig sites, such as the relatioship betwee layout pages ad cotet types, Microsoft does ot support the creatio of templates from publishig sites ad lists withi them. This lack of support is reiforced through the disablemet of template creatio liks i publishig sites. Strictly speakig, it is still possible to create templates for publishig sites ad lists by avigatig directly to the savetmpl.aspx applicatio page withi the _layouts virtual directory of a publishig site, but it is obviously ot recommeded ad supported for reasos already metioed. Settig Limits o Templates That Ca Be Geerated Aother commo barrier that users ecouter with templates is the maximum size of the template they ca create. By default, the maximum size of a list or site template that ca be created is roughly 50MB i SharePoit Attempts to create a template that is larger tha 50MB are met with a error dialog box similar to the oe show i Figure Figure Error that results from attemptig to create a template that is too large.

413 396 SharePoit 2010 Disaster Recovery Guide Storage of 50MB is typically ample for templates that iclude structural elemets without site cotet ad list items, but templates that iclude cotet from large lists ad sites ca easily exceed this limit. As a admiistrator, you have the ability to icrease or decrease the maximum size limit for list ad site templates that ed users ca geerate from withi SharePoit sites. However, before makig chages to the limit, there are a few poits worth metioig: Ay chages that you make to the maximum size limit apply to all site collectios withi the SharePoit farm. The creatio of large templates ca place a sigificat load o the Web server where the template is geerated. This ca adversely affect the performace of your SharePoit eviromet. Attempts to create templates that are too large may lead to erratic behavior ad browser timeouts. The actual poit at which udesirable behavior maifests varies from eviromet to eviromet, so you should uderstad how your farm behaves uder load before settig the maximum template creatio size to too large of a value. If chagig the maximum template creatio size is somethig you coclude that you wat to do, there are two ways to accomplish it. The recommeded approach ivolves a few simple lies of PowerShell script to chage the MaxTemplateDocumetSize property value o the cotet Web service for the SharePoit farm: $cws = [Microsoft.SharePoit.Admiistratio.SPWebService]::CotetService $cws.maxtemplatedocumetsize = <ew maximum4 $cws.update() Alteratively, you ca fall back to usig STSADM.exe to make the same chage: STSADM -o setproperty -p max-template-documet-size -pv <ew maximum4 I both the PowerShell ad STSADM.exe examples, the <ew maximum4 value specified is the ew template size creatio limit i bytes. A value of , for example, chages the maximum template creatio size to approximately 150,000,000 bytes, or 150MB, for all site collectios withi the farm. Templates ad Security As a admiistrator, there is a additioal poit you must cosider whe determiig how templates are or are ot goig to be used withi your orgaizatio: security. Although the creatio of templates that cotai oly structural iformatio do t pose much of a cocer, a user s ability to iclude list item cotet withi a template does. If sites or lists cotai sesitive cotet, that cotet ca be writte out i a template by default. Oce the cotet is writte to a

414 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 397 template ad subsequetly dowloaded, ayoe who ca access the dowloaded template has access to a copy of the cotet data that was exported. There are a couple of simple optios available to you if you wat to restrict how templates ca be created ad dowloaded. You ca tue ad reduce the maximum size of a template that ca be created. Because list item cotet ca quickly bulk-up a list, some experimetatio may allow you to set a maximum template creatio size that is adequate to allow the creatio of structural templates without permittig the creatio of templates that iclude list item cotet. By cotrollig the permissios o the List Template Gallery ad Solutio Gallery for a site collectio, you ca cotrol who ca create templates, who ca access templates, whether or ot templates ca be deleted, ad more. Additioal optios exist, particularly if you or your orgaizatio is willig to employ custom code solutios or develop special iformatio rights maagemet (IRM) policies that ca be applied to templates. Such discussios are beyod the scope of this chapter, however. WebDAV ad Explorer View Oe iterestig, yet ofte overlooked, method to access the cotets of a SharePoit site ad its lists is through Widows Explorer, usig either the Explorer View optio available o Share- Poit lists ad libraries or a protocol kow as WebDAV (for Web-based Distributed Authorig ad Versioig). SharePoit s Explorer View fuctioality opes a SharePoit library or list i Widows Explorer so that you ca maage files i a SharePoit list i the same way you maage files i a folder i a Widows operatig system. WebDAV provides most of the plumbig eeded by users to access those cotets withi the familiar folder structure of Widows Explorer via a Uiversal Namig Covetio (UNC) path. The ability to access a SharePoit site, documet library, or other type of list via Widows Explorer is pretty powerful, because it allows ed users to easily maage the files ad items i those repositories like they would ay other folders i their Widows workstatio s operatig system, rather tha usig the limited tools that are available through a browser. With the Widows Explorer iterface, a user ca drag a documet ito a SharePoit list to add it, rather tha clickig through multiple Web pages, ad do the same to copy that file back dow to his workstatio. Eve more importatly, this ca be easily doe with multiple files, which ca save time. How WebDAV ad Explorer View Are Used To access a SharePoit resource, such as a documet library, i Explorer View, avigate to the target resource i a Web browser ad click the library s Ope with Explorer butto that is preset o the Library tab of the documet library s ribbo, as show i Figure

415 398 SharePoit 2010 Disaster Recovery Guide Figure Opeig a documet library with Widows Explorer. If your SharePoit eviromet ad cliet workstatio are properly cofigured to eable Explorer View, clickig the Ope with Explorer butto lauches a istace of Widows Explorer ad avigates to the documet library. To ope a SharePoit resource directly via WebDAV, you must traslate the resource s Share- Poit URL ito a Widows Explorer friedly UNC path. You ca accomplish this by copyig the target URL ito a text file. (Do t iclude the.aspx file ame at the ed of URL; focus oly o the folder objects above that file so you ca ope the cotaiig object for the resource ad ot a item withi it.) Remove at the begiig of the address ad replace it with \\. Replace all forward slashes (/) with backslashes (\). The copy the address, paste it ito the address bar of a Widows Explorer widow, ad press Eter to load the address. The SharePoit resource ow opes as a folder withi Widows Explorer o your desktop. Like sites ad list templates, Explorer View ad WebDAV let you easily copy the cotets of a SharePoit list or documet library to your local workstatio for backup purposes ad likewise restore them to the resource as eeded. They use a familiar iterface, ad the commads to maage the files withi them are simple ad commo to Widows operatig systems. But, like site ad list templates, ed users must maually execute them, ad they are better suited to oe-time actios, whereby a ed user wats to create a copy of crucial cotet. Server ad Workstatio Cofiguratio Oe drawback with usig both Explorer View ad WebDAV is the difficulty associated with cofigurig SharePoit servers ad cliet workstatios to use them without issue o a cosistet basis. Cofiguratio o the server side of the equatio is largely a oissue thaks to the Share- Poit 2010 prerequisites istaller that rus whe SharePoit is beig set up iitially. Cliet-side cofiguratio, o the other had, is aother matter altogether. A ed user s ability to use Explorer View is greatly impacted by the combiatio of his operatig system, his Web browser, ad the versios of both items. Eve whe those are cofigured optimally (which ca be difficult i eviromets with a variety of workstatio cofiguratios), Explorer View ca be slow, proe to crashig, or simply uusable at times. Explorer View ad WebDAV also suffer from additioal depedecies o cliet cofiguratio. For WebDAV to work, for example, the WebCliet service must be ruig o the cliet

416 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 399 workstatio you re usig to access the SharePoit resource. For most cosumer operatig systems, such as Widows 7, the WebCliet service is ruig by default. If you wat to use Explorer View from a server-based operatig system, though, additioal cofiguratio steps are ofte ecessary. O Widows Server 2008 ad Widows Server 2008 R2, for example, the WebCliet service oly becomes available after eablig the Desktop Experiece feature, as show i Figure Figure Eablig a server s Desktop Experiece feature. Failure to cofigure ad eable the WebCliet service is the most commo reaso for ed users ot beig able to access a SharePoit list or documet library through Explorer View ad Web- DAV. Util the WebCliet service is ruig properly, SharePoit displays the dialog box show i Figure whe attempts are made to lauch Explorer View. Figure Message box idicatig that a cliet ca t coect usig Explorer View.

417 400 SharePoit 2010 Disaster Recovery Guide Admiistrative Cocers As stated already, most of the difficulty i gettig Explorer View ad WebDAV cofigured for use with SharePoit lies o the cliet side of the equatio. Whether or ot this impacts you depeds o the scope of your duties as a admiistrator. O the server side of thigs, there is t much for you to do either except esure that you istall SharePoit properly ad let the prerequisites istaller do its thig durig the iitial setup process. There are o readily visible kobs ad dials for the cofiguratio of Explorer View ad Web- DAV for SharePoit; SharePoit hadles ad cotrols its implemetatio iterally. Cautio: Iteret Iformatio Server 7 (IIS7) icludes its ow WebDAV Publishig role service that does ot get eabled by the SharePoit 2010 prerequisites istaller. I actuality, SharePoit 2010 supplies its WebDAV fuctioality through a private iteral implemetatio ot through IIS7. It is recommeded that you avoid eablig the IIS7 WebDAV Publishig role service o servers ruig SharePoit The jury is still out o how the WebDAV Publishig role service might impact SharePoit 2010, but eablig the role service preveted WebDAV from workig properly with SharePoit SharePoit Workspace 2010 SharePoit Workspace 2010 (SPW) is the ew kid o the block i the SharePoit product lieup or rather, oe of the existig products with a ew ame ad some ew tricks to match. Whe the Office 2010 ad SharePoit 2010 product lies were beig fleshed out, Microsoft made the decisio to take Microsoft Office Groove 2007, overhaul ad add a umber of Share- Poit 2010 specific features to it, ad rebrad the resultat product as SharePoit Workspace Although the product features that were part of Groove 2007 still exist i SPW, this sectio focuses specifically o the features that support SharePoit Groove ad related fuctios, such as peer collaboratio, are ot discussed. What Ca It Do? If you re familiar with Microsoft Exchage ad , the easiest way to explai SPW is with a aalogy. SPW s role with regard to SharePoit is aalogous to the role that the Microsoft Outlook cliet serves for Exchage servers. Although you ca access a Exchage accout usig the browser-based Outlook Web Access (OWA) cliet, usig the Microsoft Outlook rich cliet o your workstatio adds sigificat fuctioality ad improves the usability over OWA aloe. The capability that is frot ad ceter i SPW is the ability it affords you to work with Share- Poit cotet i a offlie, rich cliet applicatio settig. Whe SPW is istalled ad cofigured o your workstatio, you have the optio of creatig offlie SharePoit workspaces that are tied directly to SharePoit sites ad subsites. A example of the SharePoit Workspace for the root Web of a team site is show i Figure

418 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 401 Figure A offlie workspace for a SharePoit team site. You ca use the SharePoit Workspace cliet to iteract with SharePoit lists ad libraries, check documets i ad out, add ew cotet, ad perform most of the list ad documetcetric tasks you are used to usig a browser to perform. Note: SPW s SharePoit fuctios operate oly with SharePoit 2010 sites. You caot create workspaces that are tied to SharePoit 2007 sites. Your ability to work with SharePoit cotet is t limited to just the times you are olie ad coected. Behid the scees, SPW uses the Office Documets Cache (ODC) to track chages you make while workig offlie. Oce you evetually go back olie ad have access to the SharePoit sites associated with your chages, SPW performs bidirectioal sychroizatio to esure that both the SPW cliet ODC ad the SharePoit sites are up-to-date with the latest chages, updates, ad additios. SPW is t a complete replacemet for browser-based access to SharePoit sites, though. SPW s ability to work with lists ad libraries is tied to the cotet types that those lists ad libraries implemet. Lists ad libraries that are based o some cotet types, such as the publishig cotet types, surveys, ad evets (caledars), for example, are clearly idetified by SPW as cotet that the applicatio caot hadle.

419 402 SharePoit 2010 Disaster Recovery Guide Admiistrative Cocers SPW is the evolutio of the Groove cliet, but to may users the product is ew i the SharePoit 2010 ladscape. Oce ed users lear about it ad figure out how easily it works, you ca expect adoptio to grow quickly somethig that did t really happe with Groove. SPW s offlie capabilities are compellig, ad its ability to effectively replicate a etire SharePoit site from the server to a workstatio is udoubtedly goig to go a log way toward reassurig users that they are i cotrol of their data. These ew capabilities afford ed users a great deal of much-eeded fuctioality, but there are some admiistrative aspects that you should uderstad. Limitig the Use of SharePoit Workspace Upo learig about SPW ad how it works, the first questio uttered by may admiistrators is how do I tur it off? This is a good questio; by default, SPW ca coect to every ew site that is created withi SharePoit 2010 for purposes of establishig a cliet-side workspace. Disablig SPW support (ad offlie cliet support i geeral) ca be accomplished at two differet levels. The approach you take is drive by whether you eed to lock out a etire site or just portios of it. Site. Prevetig SPW ad other offlie cliet access to a etire SharePoit site ivolves chagig the Offlie Cliet Availability settig for the site to No. This settig is available o the Search ad Offlie Availability page that is available uder the list of Site Admiistratio liks for a selected SharePoit site. List or Documet Library. You ca block the offlie availability of a specific list or documet library through the Offlie Cliet Availability settig o the list s or library s Advaced Settigs page. By default, the optio is set to Yes to eable access to the list or library by SPW ad other offlie cliets. Chagig the optio to No blocks offlie cliet access for the list or library oly; the rest of the site remais uaffected. Cautio: Chages that are made through each of the aforemetioed settigs take effect immediately. Chagig the offlie availability settigs for a site or list/library that a ed user already has a workspace for does t sever coectios betwee SPW ad the site ad its lists/libraries, though. I fact, ed users ca cotiue to operate with a fair level of fuctioality. Operatios become somewhat upredictable, though, particularly whe SPW lauches aother applicatio (such as Microsoft Word) for editig. As a matter of policy, you should strive to set the offlie policy for your sites ad lists/libraries before ed users begi usig them. Chagig them after the fact is seldom accomplished clealy.

420 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 403 Cofiguratio Items ad Cocers To support the operatio of SPW, Microsoft actually created ad implemeted a ew file sychroizatio specificatio called the File Sychroizatio via SOAP over HTTP Protocol Specificatio, or MS-FSSHTTP. MS-FSSHTTP is a Web service-based protocol that allows for the efficiet trasfer ad sychroizatio of files betwee two edpoits. The protocol supports a umber of attractive capabilities i the offlie editig of documets that are housed i Share- Poit, such as icremetal file sychroizatio, coauthorig of documets, ad multiuser editig without sychroizatio/coflict cocers. Note: Microsoft has published the MS-FSSHTTP specificatio, ad you ca dowload it free. If you wat to lear more about the protocol ad how it operates, check it out at By ad large, SPW s ability to take files offlie ad sychroize them with a SharePoit site is oe of those thigs that simply just works from a admiistrator s perspective. Strictly speakig, there is t really aythig extra or special that you eed to do to esure that SPW ca be employed by your ed user base. That does t mea that you wo t beefit from some additioal isight, though. First, Microsoft recommeds that you eable the Remote Differetial Compressio (RDC) feature o Widows servers where offlie cliets are coectig. Although cliets that employ the MS-FSSHTTP protocol for coectios to the SharePoit eviromet support icremetal file trasfers ad other beefits already metioed, other offlie cliets such as older versios of Microsoft Office do ot. RDC complemets MS-FSSHTP ad eables the efficiet upload ad dowload of icremetal file chages o these other offlie cliet types. Without RDC eabled, the upload ad dowload of a etire file is eeded whe a older cliet type is performig a icremetal chage oly. RDC is ot eabled by default o Widows Server 2008, ad it is t eabled by the SharePoit 2010 prerequisites istaller. You must maually eable the RDC server feature from either the commad lie or usig the Widows Server Add Features Wizard. Offlie Operatios ad Security Aother area you should be cocered about whe allowig SPW usage is security. As a admiistrator, you eed to address two specific areas: Trasport layer security. By default, commuicatios betwee SPW ad the SharePoit eviromet take place through the URL edpoit that ed users supply whe settig up a SPW workspace o their workstatios. If the URL that is supplied does t map to a edpoit that supports some form of trasport layer security such as Secure Socket Layer (SSL) ecryptio, ed users are goig to be trasmittig the cotets of lists ad libraries across the

421 404 SharePoit 2010 Disaster Recovery Guide wire i uecrypted form. This really is o differet from other forms of access to the SharePoit site through the edpoit specified, but the sheer volume of file traffic that occurs with SPW warrats this special metio. Cliet storage security. SPW uses the ODC for offlie SharePoit list ad library storage. Although SPW is capable of ecryptig some Groove-related data, SharePoit file ad ofile data is ot ecrypted o ed user workstatios. This meas that the cotets of each SharePoit workspace (that is, the lists ad libraries that are withi the associated Share- Poit site) reside o ed user workstatios i uecrypted form. The cotets of these offlie files are t huma readable, but the fact that they are t ecrypted wo t stop someoe determied to read them. If data protectio is a cocer, you must employ a secodary form of ecryptio (such as Widows BitLocker drive ecryptio). Sychroizig Large Numbers of Documets Although SharePoit sychroizatio with SPW simply works i the majority of cases, you eed to be aware of a couple of thresholds whe workig with large umbers of cliet-side documets that are tied to SharePoit sites through workspaces. The first threshold is hit whe SPW attempts to sychroize approximately 500 or more documets betwee SharePoit sites ad all cliet-side workspaces. Whe this threshold is hit, you are wared that you eed to free up some space o your workstatio. You ca safely igore this warig, but icreasig the umber of offlie SharePoit documets yields icreased sychroizatio overhead that may result i a degraded experiece ad poorer performace. A more dramatic threshold is hit whe the total umber of offlie documets across all workspaces exceeds At this poit, SharePoit Workspace switches from regular sychroizatio of all documet cotet ad metadata to regular sychroizatio of documet metadata oly. Ay time a documet is targeted for actio or modificatio, the documet cotet is sychroized o demad to esure that you have a valid copy. This o-demad cotet sychroizatio behavior allows SPW to limit what would otherwise be excessive overhead ad performace degradatio. Brigig SPW back to a poit that is below the documet thresholds metioed is as simple as discardig local SharePoit documets, deletig uused SharePoit workspaces, ad discoectig from uused or ueeded documet libraries. As a geeral rule of thumb, the fewer the umber of offlie documets you have o your workstatio, the better your performace will be with SPW sychroizatio. Coclusio SharePoit 2010 provides ed users with a umber of tools that provide some level of protectio agaist data loss, udesired chages, ad SharePoit site outage scearios. Recycle Bis, versioig, the creatio of templates, Explorer View, WebDAV, ad SharePoit Workspace 2010 all meet differet eeds for differet ed users. Although oe of these tools plays a sigificat role

422 Chapter 12 SharePoit 2010 Disaster Recovery for Ed Users 405 i the overall disaster recovery strategy that you are resposible for developig ad maitaiig, these tools ca help promote ed user self-sufficiecy for some of the lesser data protectio ad recovery tasks you would be tasked with hadlig otherwise. At a miimum, each of the ed user tools ad techiques that have bee described i this chapter demads some level of operatioal awareess o your part. Some of the features, such as Recycle Bis ad templates, require some actual admiistrative cofiguratio o your part. Regardless of your ow persoal leaigs, it is likely i your best iterests as a admiistrator to uderstad what ed users ca do to protect ad recover data i the SharePoit eviromet. The ext support call you get may be resolved more quickly if you are able to direct users to oe of the tools or techiques described i this chapter. Havig completed this chapter, you should ow be able to aswer the followig questios. As with the other chapters, aswers to the followig questios appear i Appedix A, Chapter Review Q&A, foud o the Cegage Learig Web site at dowloads. 1. What are the maximum storage limits that are i place for the first ad secod stage Recycle Bis for a site collectio created o a Web applicatio with default settigs? 2. How do you eable versioig o a list or library? 3. What is the primary security cocer associated with site ad list template creatio? 4. What key service must be istalled ad fuctioal for cliet-side WebDAV access to a SharePoit list or library? 5. How do you tur off SharePoit Workspace 2010 access to a SharePoit list or documet library? To a etire SharePoit site?

423 This page itetioally left blak

424 13 Coclusio You ve fiished the book, ad hopefully you ve preserved your saity by readig chapters ad sectios here ad there as eeded. We packed a awful lot of iformatio ito this book, ad it s hard to pull it all i at oce ad process it without comig up for air. If you did t pace yourself ad you re oe of those die-hard troopers who read the book from cover to cover, we salute you! You are ideed a rare breed the type that probably wids dow at ight readig patet applicatios, istructio mauals, ad a radomly selected book from the ecyclopedia set o the shelf. Regardless of how you idetify yourself as a reader, we hope that you foud each of the chapters betwee the covers to be helpful, iformative, ad referetial. We spet may log hours writig ad refiig the cotet i this book. Our goal was to provide you, the admiistrator, with the material you would eed to uderstad ad carry out disaster recovery plaig for your SharePoit eviromet i a iformed ad educated maer. If we did our jobs properly, the structural itegrity of your craium is probably somewhat compromised from the costat drummig we have bee doig throughout may of the chapters. Regardless of who you are or why you picked up this book, we made the reasoable assumptio that you have at least some iterest i SharePoit disaster recovery. With that i mid, we tried to drive home a hadful of uiversal cocepts wheever ad wherever we could. The most importat cocept we tried to drive home bears repeatig oe more time as a partig shot: there is o such thig as a oe-size-fits-all SharePoit disaster recovery strategy. Although there are some patters that do arise i SharePoit disaster recovery plaig ad implemetatio, your eviromet is uique. You may have some luck i startig with a template that was desiged by someoe else with disaster recovery eeds that were similar to yours, but by ow you should fully uderstad why ay such template or prepackaged strategy is merely a startig poit ot the ed of the coversatio. You should also realize that disaster recovery is a awful lot more tha just backup ad restore. Some admiistrators fall ito the habit of usig disaster recovery ad backup/restore iterchageably, but they are ot syoymous. The latter is ofte a major facet of the former, but disaster recovery activities are drive primarily by busiess cocers ot techical cocers as 407

425 408 SharePoit 2010 Disaster Recovery Guide i the case of backup/restore. If ay of this souds a little fuzzy, go back ad reread the first few chapters of the book. It s okay, ad we uderstad. The material was covered quite some time ago if you re oe of the aforemetioed die-hard, cover-to-cover readers. Microsoft has packed some great ew disaster recovery features ad capabilities ito the SharePoit 2010 platform, ad we ve attempted to cover as may of them as possible i this book. Much as there is o oe-size-fits-all approach to disaster recovery i geeral, there is o magic bullet feature that is goig to address your disaster recovery eeds i every sceario. Every techology supportig disaster recovery comes with its ow beefits ad disadvatages, ad we have tried to provide you with the iformatio eeded to compare the platform features ad uderstad where each of them excels ad comes up short. After all the disaster recovery strategies have bee plotted, the techologies have bee selected, ad the plas have bee built, you still have to deal with the day-to-day operatioal cocers that remai i the disaster recovery bucket. Backups, restores, recoveries, ad rebuilds are some of the activities that ted to get tossed ito that bucket. We covered may of these cocers ad operatig scearios i several of the chapters, ad we tried to address the challeges ad questios that we ourselves have see i our SharePoit travels. We hope that you foud the material to be useful i your role as a admiistrator. Eve though we maaged to go o about SharePoit disaster recovery for more tha 400 pages, we would be lyig if we said that we were able to cover all the techologies, cocers, scearios, ad watch-outs that we would have liked. We had to make some compromises o coverage, ad where we did, we attempted to call those out. If you foud somethig particularly helpful, we would love to hear about it. At the same time, we wat to hear about troubles you ve had, techologies we should have covered, situatios that have frustrated you, ad aythig else you wat to share that is disaster recovery related. We closed our 2007 versio of this book with the followig quote, ad it remais just as applicable ow as it did before. The followig is attributed to Ala Lakei, a ackowledged expert o persoal time maagemet: Plaig is brigig the future ito the preset so that you ca do somethig about it ow. These words summarize the essece of disaster recovery plaig i a utshell. Disasters do t happe whe it s orgaizatioally coveiet, ad they strike without warig. The oly reasoable course of actio is to assume that a disaster will happe to your SharePoit eviromet at some poit i the future ad work to prepare for that disaster ow. After all, hope ad igorace are ot recogized as acceptable risk mitigatio strategies i ay techical group or orgaizatio.

426 Idex A AAMs (alterate access mappigs), 203, 327, 371 access Graular Backups, 264 Maagemet Shell, etworks, UAG (Uified Access Gateway), 37 Access Cotrol optio, 82 accouts Cetral Admiistratio, services, 234 user, 264 acquirig resources, Active Directory. See AD AD (Active Directory), 8, 44 review of, 19 Add Features Wizard, 67 addig servers to farms, Add Iteral URLs page, 204 addresses IPAM (IP address maagemet), 8 MAC (Media Access Cotrol), 121 Address Resolutio Protocol. See ARP Add-SPShellAdmi rights, 303 admiistratio Cetral Admiistratio, 54 Explorer View, 400 Microsoft SharePoit Workspace 2010, 402 templates, versioig, WebDAV, 400 Admiistratio.cofig file, 60 admiistrator roles, Advaced Settigs butto, 88 affiity, 121, 126 agets, log shippig, 193 alerts, log shippig, 192 aliases, SQL (Structured Query Laguage), 224, 371 alterate access mappigs. See AAMs aalysis As-Is, 31 BIA (busiess impact aalysis), 3 techical, 14 To-Be, 31 aual cost of disaster recovery, 32 ativirus software backups, 259 database clusters, istallig o, 234 APIs (applicatio programmig iterfaces), 45, 170 Cotet Deploymet API, 257, AppCmd.exe tool, 69, 78 ApplicatioHost.cofig file, 60 applicatio programmig iterfaces. See APIs applicatios. See also software catastrophic backups, 245 for disaster recovery readiess, loggig, moitorig, Service Applicatio, 10, 170 services, 7, 16, 138 Web Applicatios, 7 quota templates, Recycle Bi settigs, Web Service Applicatios, applyig catastrophic backups, Graular Backups, approaches to backup strategies, architecture logical, 7 8 Search, archives, cabiet (.cab), 51 ARP (Address Resolutio Protocol), 129 arrays, RAID (Redudat Array of Idepedet Disks), 19 As-Is aalysis, 31 assemblies GAC (Global Assembly Cache), maagemet,

427 410 SharePoit 2010 Disaster Recovery Guide assessmet ad plaig, 6 11 risk, 3 AssigmetCollectio parameter, 308, 311, 316, 320, 322, assumptios, 20 asychroous operatig mode, database mirrorig, 222 audiece, 20 auditig, 387 automatig database clusterig, 237 database mirrorig, 229 B back-ed databases, See also databases Back Up Database dialog box, 154, 162, 174 Backup Directory Locatio, 288 BackupID parameter, 323 BackupMethod parameter, 308 Backup Oce Wizard, 83, Backup Progress dialog box, 90 backups, approaches, catastrophic, catastrophic cmdlets, Cetral Admiistratio, , See also Cetral Admiistratio certificates, 61 compatibility, 166 compressio, 165 cofiguratio folders, 60 cofiguratio-oly backups, , 346 customizatios, databases clusterig, 238 sapshots, types, depedecies, 63 destiatios, 162 expiratio, cofigurig, 162 farms, 244 files, folders, full farm catastrophic, Cetral Admiistratio, Get-SPBackupHistory cmdlet, graular backup ad restore, Graular Backups, idividual compoet backups, lauchig, 85 locatios, 83, log shippig, 191, 206 mirrored media sets, 164 moitorig, 86 Overwrite Media sectio, paths, plaig, PowerShell prerequisites, prerequisites, providers, 63 reliability checks, 163 schedules, 81 selectig, 87 serializatio, 252 shared etwork folders, 82 site collectio, , Site Collectio Backups, SQL Server 2008, databases, ew features, restorig, storage locatios, selectig, targets, Widows Registry, Widows Server 2008, Widows Server Backup features, 78 eablig, storage, 77 Backup Schedule Wizard, 79, 83 Backup Set sectio, 162 BackupSettigs.aspx page, 261 Backup-SPCofiguratioDatabase cmdlet, Backup-SPFarm cmdlet, Backup-SPSite cmdlet, BackupThreads parameter, 308.bak files, 252 badwidth, etworks, 224 baselies, recovery, 19 BCP (busiess cotiuity plaig), 3, 14 backup schedules, 81 testig, 26 BCS (Busiess Coectivity Services), 7, 247 beefits of versioig, 386 best practices fuctioality, 36 scope, determiig, tools, BIA (busiess impact aalysis), 3, 14 BLOB (Biary Large Object), 166, 247 bottleecks, 25 breadth of eviromets, 47 budgets determiig, 39 maiteace, 32 buildig stadby farms, Bulk-Logged recovery model, 159 Busiess Coectivity Services. See BCS

428 Idex 411 busiess cotiuity plaig. See BCP busiess data, 10 busiess impact aalysis. See BIA busiess owers, 6 C cabiet (.cab) archive file, 51 caches cofigurig, 137 GAC (Global Assembly Cache), Cacti, 43 calculatig budgets, 32 capabilities, 20 of tools, determiig, capture completeess, log shippig, 206 CAS (cotet addressable stores), 166 case sesitivity, 193 PowerShell, 304 catastrophic backups, applyig, cmdlets, catastrophic restore cmdlets, Cetral Admiistratio, 54, accouts, backups, cofigurig, capabilities, cofiguratio-oly backups, cotet, exportig, differetial backups, 265 full backups, 265 full farm catastrophic backups, Graular Backups, overview of, permissios, restorig, services, site collectio backups, uattached cotet database data recovery, cetrally maaged customizatios, 51 cetral processig uits. See CPUs certificates servers, 94 SSL (Secure Socket Layer), 61, 93 95, 114 verifyig, 95 Certificates MMC sap-i, 62, 78 chages maagemet, 43 trackig, 387 checklists, verifyig, Choose Additioal Restore Optios dialog box, 104 classificatios of backup targets, cliets security, 404 SQL Server Maagemet Studio, 153 Cluster Admiistrator tool, 235 clusters databases, amig, 235 NLB (Widows Network Load Balacig), cofigurig, 119 servers, 145 SQL Sever 2008, 39 Cluster Validatio Tool (CVT), 232 cmdlets Backup-SPCofiguratioDatabase, Backup-SPFarm, Backup-SPSite, catastrophic backup, catastrophic restore, Export-SPWeb, Import-SPWeb, Restore-SPFarm, Restore-SPSite, cmp files, 257 collectios host-amed site, 326 Site Collectio Backups, sites, COM (compoet object model), 352 Commad-Lie Tools optio, 67 commuicatio ecouragig, 29 plas, compatibility backups, 166 database clusterig, 238 Complete the Wizard scree, 218 complexity, maagig, 38 compoet object model. See COM compoets catastrophic backup files, 254 preservig, 37 restorig, servers database clusterig, database mirrorig, of log shippig, 191 testig, 27 validatig, 236 VSS (Volume Shadow Copy Service), 359 compressio backups, 165 hard drives, 234 cocepts, 3 6 coductig testig, Cofig directory, 254

429 412 SharePoit 2010 Disaster Recovery Guide cofiguratio affiity, 126 backups Cetral Admiistratio, expiratio, 162 selectig, 79 caches, 137 cofiguratio-oly backup ad restore, 346 data, 9 databases, 200 documetatio, edpoits, 218 Explorer View, hardware, 137 histories, 61 IIS, 60 61, 91 92, log shippig, , 205 Microsoft SharePoit Workspace 2010, Microsoft System Ceter Cofiguratio Maager, 92 mirrorig databases, , etworks, 137, NLB (Microsoft Network Load Balacig), 119, pricipal servers, 214 Recycle Bis, versioig, WebDAV, Widows Registry, Widows Server 2008 failover clusterig, cofiguratio-oly backups, CofiguratioOly parameter, 309, 312, 322, 324 Cofigure Backup Settigs lik, 260 Cofigure Database Mirrorig Security Wizard, 212 Cofigure Security butto, 211 cofirmatio backup schedule parameters, 84 istallatios, 70 recovery, 111 Cofirm parameter, 309, 320, , 325 coectios database clusterig, 233 as recovery targets, 15 SQL Server 2008 backups, 153 Coectios TreeView cotrol, 93 cotet databases, 7, 202, exportig, 257, , 296 mirrorig database, 225 recovery, 14, 17, restorig, verifyig, 21 cotet addressable stores. See CAS CotetDatabase parameter, 325 Cotet Deploymet API, 257, cotiuity, BCP (busiess cotiuity plaig), 3 cotrollers, domais, 8 cotrols, Coectios TreeView, 93 copyig files, 197 log shippig, 191 VMs (virtual machies), 41 copy-oly backups, 161 costs database clusterig, 239 determiig, 39 implemetatio, 17 log shippig, 205 maiteace, 32 covered systems, 20 CPUs (cetral processig uits), performace, 165 Crawl servers, 140 CREATE DATABASE permissios, 172 Create New Web Applicatio dialog box, 56 credetials security, 300 CU (Cumulative Update) packages, 150 curret states, moitorig, 43 customizatio backups, cofiguratio-oly backups, 259 disaster recovery, CVT (Cluster Validatio Tool), 232 D database admiistrators. See DBAs DatabaseCredetials parameter, 316 database ecryptio key. See DEK DatabaseName parameter, , 327 Database Properties dialog box, 193, 211 databases backups sapshots, types, clusterig, cotet, 7 HA (high availability), 202 log shippig, mirrorig, optios, recovery models, targets, 14 restorig cotet, distributio, 15 sizig, SQL Server 2008 backups, uattached cotet,

430 Idex 413 DatabaseServer parameter, 317, 327 data loss, log shippig, 207 DBAs (database admiistrators), 16, 150 db_backoperator security role, 153 decetralized customizatios, 51 52, 54 Ietpub folder, 57 Default zoe mappig, 55 defiig commuicatio plas, recovery targets, scope, 13 14, success of recoveries, 22 defiitio process, scope, 16 DEK (database ecryptio key), 247 depedecies, 10 11, 20, 25 backups, 63 depedet services, testig, 27 depedet systems, restorig, 16 deploymet Cotet Deploymet API, physical, 8 9 depth of eviromets, 47 desig, documetatio of, destiatios backups, 162 optios, restorig, types, specifyig backups, 89 developmet disaster recovery, 337.NET, 361 VSS (Volume Shadow Copy Service), devices, IPAM (IP address maagemet), 8 DFS (Distributed File System), 371 DHCP (Dyamic Host Cofiguratio Protocol), 19 diagostics logs, 53 settigs, 259 dialog boxes Back Up Database, 154, 162, 174 Backup Progress, 90 Choose Additioal Restore Optios, 104 Create New Web Applicatio, 56 Database Properties, 193, 211 Edit System Variable, 71, 75 Eviromet Variables, 70, 75 Export Certificate, 94 Log Shippig Moitor Settigs, 201 Register Backup Schedule, 82 Re-Image Your Computer, 100 Restore Database, 173, 210 Ru, 68 Secodary Database Settigs, 197 Select Items, 88 Select Remote Folder, 88 System Properties, 70 71, 74 Trasactio Log Backup Settigs, 194 Versio History, 386 differetial backups, 160 Cetral Admiistratio, 265 directories Backup Directory Locatio, 288 catastrophic backups, 248 Cofig, 254 Ietpub, Microsoft Office Servers, 52 Program Files, 52 Directory parameter, 308, 316, , 324 disaster recovery, 2 3. See also recovery applicatios for readiess, chages i SharePoit 2010, 376 customizig, developmet, 337 ed users, discovery, 6 10 disks, quorum, 234 Distributed File System. See DFS distributio databases mirrorig, 229 restorig, 15 log shippig, 206 DNS (Domai Name Services), 19, 235, 370 DocAve Exteder, 167 documetatio, 6 10, 32 cofiguratio, desig, ifrastructure, procedures for outages, Service Applicatio, 10 TechNet, 92 documet sychroizatio, 404 domai cotrollers, 8 Domai Name Services. See DNS draft versioig, 386 DVDs, as backups, 74 Dyamic Host Cofiguratio Protocol. See DHCP E Edit System Variable dialog box, 71, 75 effective dates, 20 backups, 259 eablig backup compressio, 165 database clusterig, 234 full server backups, 78 log shippig, server desktop features, 399 Widows Server Backup features, ecouragig commuicatio, 29

431 414 SharePoit 2010 Disaster Recovery Guide ecryptio DEK (database ecryptio key), 247 TDE (Trasparet Data Ecryptio), 166 edpoits, cofigurig, 218 ed users, disaster recovery, eviromets modifyig, testig, 50 usage, determiig, 37 Eviromet Variables dialog box, 70, 75 errors, log shippig, 207 Excel Services Service Applicatio, 14 expiratio, cofigurig backups, 162 Explorer View, Export Certificate dialog box, 94 exportig certificates, verifyig, 95 cotet, 257, , 296 Widows Registry, 97 Export-SPWeb cmdlet, exteral hard disks, backups, 76 F failover clusters, SQL Server 2008, 39 Widows Server 2008, cofigurig, Farm Backup ad Restore, accessig, 264 FarmCredetials parameter, farms, 5 backups, 244 budgets, calculatig, 32 documetatio, 6 10 load balacig, maiteace, 32 restorig, servers, addig, stadby, buildig, FAST, 8 FAT32, 77 fault tolerace, database clusterig, 239 FB (Fiber Chael), 233 files. See also directories Admiistratio.cofig, 60 ApplicatioHost.cofig, 60 backups, 86 91, 161, bak, 252 cabiet (.cab) archive, 51 catastrophic backups, viewig, cmp, 257 copyig, 197 Hosts, 204 out-of-the-box image, 53 Redirectio.cofig, 60 resource (.resx), 51 restorig, sharig, log shippig, 192 spbackup.log, 252 spbackup.xml, 252 spbrtoc.xml, 249 sprestore.log, 254 sprestore.xml, 254 web.cofig, 57 FILESTREAM provider, 167 log shippig, 206 firewalls, 38 folders. See also directories backups, remote shared, 74 restorig, root, 55 Force parameter, 309, 320, 323, 326 Foudatio VSS writers, roles of, 360 frequecy of backups, 81 full backups Cetral Admiistratio, 265 databases, 160 full-farm catastrophic backups, See also backups Cetral Admiistratio, full recovery models, SQL Server 2008 database backups, full server backups, 64 Widows Server 2008, full server recovery, fuctioality, 36 G GAC (Global Assembly Cache), gateways TMG (Threat Maagemet Gateway), 37 UAG (Uified Access Gateway), 37 GB/s (gigabyte per secod), 224 Get-Help cmdlet, 304 Get-SPBackupHistory cmdlet, gigabyte per secod (GB/s), 224 Global Assembly Cache. See GAC glossary of terms, 20 GradualDelete parameter, 326 graular backup ad restore, , access, 264 graphical user iterfaces. See GUIs groups, OMG (Object Maagemet Group), 7 GUIs (graphical user iterfaces), database mirrorig, 225

432 Idex 415 H HA (high availability), 117, databases clusterig, mirrorig, log shippig, SQL Server 2008, trasactio log backups, 161 hard disk backups, 75 hard drive compressio, 234 hardware acquirig, 19 cofigurig, 137 load balacig, RAID, 143 HCL (Hardware Compatibility List), 232 health moitorig, 121 heartbeats, 235 high availability. See HA HIPAA (Health Isurace Portability ad Accoutability Act), 10 histories cofiguratio, 61 Get-SPBackupHistory cmdlet, restorig, Host file, 204 HostHeaderWebApplicatioURL parameter, 325 host-amed site collectios, 7, 326 Hyper-V, 41, 98 I IBackupRestore, idetical cofiguratios, database clusterig, 232 Idetity parameter, 325 IIS (Iteret Iformatio Services), 7, 51, cofiguratio, Ietpub directory, Maager, 59 restorig, images, system, 101, 103 implemetatio, 13 costs, 17 recovery targets, restorig, determiig recovery targets, scope defiig, determiig out of, 16 Import-SPWeb cmdlet, idepedece database mirrorig, 229 log shippig, 205 idexes, partitios, 140 idividual compoets backups, 65 restorig, Widows Server 2008, IetMgr.exe, 78 Ietpub directory, IfoPath, 11 iformatio rights maagemet (IRM), 259 ifrastructure documetatio, moitorig, 43 etworks, plaig, iput/output. See I/O istallatios, cofirmig, 70 istaces, amig, 224, 236 itegratio, FAST, 8 iterfaces, See also UIs (user iterfaces) APIs (applicatio programmig iterfaces), 45 Cotet Deploymet API, 257 database mirrorig, 225 restorig, 16 SQL Server Maagemet Studio, 153 iteral hard disk backups, 75 Iteret Iformatio Services. See IIS Iteret Protocol (IP), 233 Iteret SCSI (iscsi), 233 Iteret Security ad Acceleratio. See ISA Iteret Storage Namig Server (isns), 145 I/O (iput/output), 37, 164 IP (Iteret Protocol), 233 IP address maagemet. See IPAM IPAM (IP address maagemet), 8 IRM (iformatio rights maagemet), 259 ISA (Iteret Security ad Acceleratio), 38 iscsi (Iteret SCSI), 233 isns (Iteret Storage Namig Server), 145 Item parameter, 309, 312, 317, items, selectig backups, 88 J K jobs, log shippig, Job Schedule Properties widow, 196 keys, DEK (database ecryptio key), 247 key terms, 3 6 L laguages, UML (Uified Modelig Laguage), 7 LANs (local area etworks), backup compressio, 165 large umber of documets, sychroizig, 404 latecy database mirrorig, 208, 223 log shippig, 207

433 416 SharePoit 2010 Disaster Recovery Guide lauchig backups, 85 database mirrorig, 219 Server Maager, 67 layers, SSL (Secure Socket Layer), 61. See also SSL Secure Socket Layer) LDRPS (Livig Disaster Recovery Plaig System), 32 leveragig site collectio backup ad restore, liceses acquirig, 19 database mirrorig, log shippig, 192 SQL Server 2008, 166 limitatios of Microsoft SharePoit Workspace 2010, 402 o templates, lists defiitios, 51 templates, Livig Disaster Recovery Plaig System (LDRPS), 32 load balacig, farms, hardware, software, local area etworks. See LANs locatios Backup Directory Locatio, 288 backups, 83 files, media, 169 selectig, 101 logical architecture, 7 8 logs applicatios, diagostics, 53 shippig, , 238 Log Shippig Moitor Settigs dialog box, 201 losses, plaig for, 28 M MAC (Media Access Cotrol) addresses, 121 maiteace costs, 32 plaig, major versioig, 386 Maage Cotet Databases page, 226 maagemet assemblies, 51 Cetral Admiistratio, 54. See Cetral Admiistratio chage maagemet, 43 complexity, 38 failover clusterig, 235 IIS (Iteret Iformatio Services), 59 IPAM (IP address maagemet), 8 IRM (iformatio rights maagemet), 259 Microsoft System Ceter Cofiguratio Maager, 92 OMG (Object Maagemet Group), 7 resources, SCOM (System Ceter Operatios Maager), 121 Server Maager, 67 SQL Server Maagemet Studio, 153 threads, TMG (Threat Maagemet Gateway), 37 of versios, 387 Maagemet Shell, accessig, maually failig database mirrorig, 221 mapped etwork drives, 371 mappig, 7 AAMs (alterate access mappigs), 203, 327 Default zoe, 55 MASTER databases, 169 Media Access Cotrol addresses. See MAC address meus, Script, 154 Microsoft Cluster Service. See MSCS Microsoft Maagemet Cosole. See MMC Microsoft Office Servers directory, 52 Microsoft Office SharePoit Server (MOSS) 2007, 138 Microsoft SharePoit Desiger 2010, 376 templates, 394 Microsoft SharePoit Workspace 2010, 376, Microsoft System Ceter Cofiguratio Maager, 92 Microsoft TechNet, 257 mior versioig, 386 mirrorig databases, media sets, backups, 164 Mirror Server Istace scree, 214 mixig backup types, 265 MMC (Microsoft Maagemet Cosole), 61, 263 MODEL databases, 169 models Bulk-Logged recovery, SQL Server 2008 database backups, 159 objects, , recovery databases, SQL Server 2008 database backups, simple recovery, SQL Server 2008 database backups, modifyig cotet database cofiguratio, 295 eviromets, Path text box, 56 plaig, web.cofig files, 57

434 Idex 417 moitorig applicatios, backups, 86 curret states, 43 health, 121 recovery, 112 MOSS (Microsoft Office SharePoit Server) 2007, 138 moutig shared storage, 234 MSCS (Microsoft Clusterig Services), 120, 232 MSDB databases, 169 Multicast mode, N amig clusters, 235 DNS (Domai Name Services), 19 istaces, 224, 236 isns (Iteret Storage Namig Server), 145 virtual servers, 236 NAS (etwork-attached storage), 8, 76 NDIS (Network Driver Iterface Specificatio), 121.NET developmet, 361 GAC (Global Assembly Cache), NetBIOS (Network Basic Iput/Output System), 233 etwork-attached storage. See NAS Network Basic Iput/Output System. See NetBIOS Network Driver Iterface Specificatio (NDIS), 121 etwork file system. See NTFS etwork iterface cards. See NICs etworks access, badwidth, 224 cofigurig, 137, ifrastructure, plaig, requiremets, database clusterig, 238 resources, database clusterig, 233 WANs (wide area etworks), 8 NewDatabaseServer parameter, 322 ew features SQL Server 2008 backups, Widow Server 2008, NICs (etwork iterface cards), 233 NLB (Microsoft Network Load Balacig), cofigurig, operatioal modes, NoSiteLock parameter, 320 NTFS (etwork file system), 77 self-healig, 144 O Object Maagemet Group. See OMG objects, models, , observig, 30 OMG (Object Maagemet Group), 7 operatig systems. See OS operatioal modes, NLB (Microsoft Network Load Balacig), operatios Microsoft SharePoit Workspace 2010, mode, database mirrorig, 225 optimizig I/O (iput/output), 164 optios Commad-Lie Tools, 67 databases, destiatios, restorig, 104, Tasks Back Up meu, 155 OS (operatig systems), 49 outages patchig without, 238 procedures for, documetatio, scope, defiig, out of scope, 16 out-of-the-box image files, 53 Overwrite Media sectio, backups, overwritig restore of SQL backups, owers, 6 P packages, CU (Cumulative Update), 150 Page View Web Part, 11 parameters, certificates, 94 partial backups, partitios, idexes, 140 patchig without outages, 238 Path parameter, 325 paths backups, qualificatio, 72 Path text box, modifyig, 56 pausig database mirrorig, 221 people, testig, 28 Percetage parameter, 309, 323 performace, 37 backup compressio, 165 database mirrorig, 228 log shippig, 206 Widows Performace Moitor, 43 PerformacePoit Services, 8 permissios Cetral Admiistratio, CREATE DATABASE, 172 database mirrorig, 211, 224 physical computig resources, database mirrorig, 224 physical deploymet, 8 9 physical limitatios of recovery plaig, 18 physical requiremets, determiig, 18 19

435 418 SharePoit 2010 Disaster Recovery Guide physical servers, 8 plaig, 2 3, assessmet ad, 6 11 backups, BCP (busiess cotiuity plaig), 3 commuicatio, desig documetatio, for losses, 28 maiteace, modifyig, etwork ifrastructure, PowerShell, recovery, redesigig, 30 scope, defiig, testig, validatig, 30 VMs (virtual machies), 98 policies, Web applicatios, 7 poor status visibility, log shippig, 207 PowerShell, 69 admiistrative capabilities, backup prerequisites, case sesitivity, 304 graular backup ad restore, plaig, scripts, 301 support, 121 preparedess, verifyig, prerequisites, 20 backups, full server recovery, 98 PowerShell backups, preservig compoets, 37 primary cotet, 20. See also cotet pricipal databases, 209 pricipal servers, cofigurig, 214 priorities, 38 procedures for outages, documetatio, process recovery. See recovery Program Files directory, 52 progress, trackig, 105 providers, 359 backups, 63 publishig sites, templates ad, 395 purpose, 20 Q qualificatio, paths, 72 queries, 205. See also searchig Query servers, 140 quorum disks, 234 quota templates, Web Applicatios, R RAID (Redudat Arrays of Idepedet (or Iexpesive) Disks), 19, rapid failover, 238 RBS (Remote Biary Large Object Storage), 10, 166, 247 RCW (rutime callable wrapper), 361 RDC (Remote Differetial Compressio), 403 Readiess area (for Perform a Backup), 263 read-oly availability, log shippig, 205 recommedatios, database mirrorig, recordig iformatio, 29 recovery baselies, 19 best practices. See best practices cofirmig, 111 cotet, databases mirrorig, 211, 224 models, desig documetatio, full server, log shippig, 193 lowerig impact of, 21 maiteace, moitorig, 112 plaig, poit objective. See RPO progress, trackig, 105 state, success, 22 targets, determiig, preservig, 37 time objective. See RTO uattached cotet database data, VMs (virtual machies), 98 Recovery Wizard, 106 Recycle Bis, cofiguratio, redesigig, plaig, 30 Redirectio.cofig file, 60 redudacy databases clusterig, 233 mirrorig, 229 log shippig, 206 Redudat Arrays of Idepedet (or Iexpesive) Disks (RAID), refereces, 20 RegEdit.exe, 78 Register Backup Schedule dialog box, 82 Registry (Widows) backups, restorig, 115

436 Idex 419 Registry Editor tool, Re-Image Your Computer dialog box, 100 relatioships, trust, 292 reliability checks, backups, 163 Remote Biary Large Object Storage. See RBS Remote Differetial Compressio (RDC), 403 remote folders, specifyig, 90 remote shared folders, 74 removable media, backups, 74 requestors, 359 requiremets database mirrorig, determiig, etworks, database clusterig, 238 for recovery, 5 resource (.resx) files, 51 resources acquirig, costs, 32 determiig, maagig, etworks, database clusterig, 233 securig, 21 testig, 27 resposibilities, 20 restartig servers followig recovery, 105 Restore Database dialog box, 173, 210 RestoreMethod parameter, 322 Restore-SPFarm cmdlet, Restore-SPSite cmdlet, RestoreThreads parameter, 322 restorig, backups, catastrophic restore cmdlets, Cetral Admiistratio, , See also Cetral Admiistratio cofiguratio-oly backup ad restore, 346 cotet, 15 16, destiatio optios, determiig recovery targets, farms, files, folders, graular backup ad restore, IIS cofiguratio, idividual compoets, log shippig, 192 optios, 104, PowerShell prerequisites, services, 37 site collectio, source optios, SSL certificates, 114 Widows Registry, 115 Widows Server 2008, revisio history, 20 rights Add-SPShellAdmi, 303 IRM (iformatio rights maagemet), 259 risk, 3 roles, 20 admiistrators, Foudatio VSS writers, 360 Search, security, db_backoperator, 153 SharePoit_Shell_Access, 303 Root (SharePoit), root folders, 55 RPOs (recovery poit objectives), 4 backups, 63 plaig, 17 priorities, 38 testig, 26 tools, 46 Widows Server Backup, 80 RTOs (recovery time objectives), 4 backups, 63 cotet recovery, 268 log shippig, 202 plaig, 17 priorities, 38 testig, 26 tools, 46 Ru dialog box, 68 rutime callable wrapper. See RCW S salability, database clusterig, 238 SANs (storage area etworks), 8, 76 acquirig, 19 costs, 39 HA (high availability), 144 NLB (Widows Network Load Balacig), 120 requiremets, database clusterig, 238 usage, determiig, 37 Sarbaes-Oxley Act (2002), 10 schedules backups, 81 Backup Schedule Wizard, 79, 83 Job Schedule Properties widow, 196 SCOM (System Ceter Operatios Maager), 121 scope, 20 defiig, determiig, out of, 16 Script meu, 154 scripts backup ad restore cmdlets, PowerShell, 301

437 420 SharePoit 2010 Disaster Recovery Guide SCSI (Small Computer System Iterface), 233 search databases, log shippig, 200 searchig, FAST, 8 Search roles, Secodary Database Settigs dialog box, 197 Secure Socket Layer. See SSL Secure Store Service Applicatio, 247 securig items, idetifyig, 21 security, 38 Cetral Admiistratio, cliets, 404 cofiguratio data, 9 Cofigure Database Mirrorig Security Wizard, 212 Cofigure Security butto, 211 credetials, 300 database mirrorig, 208 DEK (database ecryptio key), 247 Microsoft SharePoit Workspace 2010, roles, db_backoperator, 153 templates, trasport layer security, 403 selectig backups, 87 approaches, cofiguratios, 79 RPOs or RTOs, 5 storage locatio backups, system images, 103 types of catastrophic backups, 245 Select Items dialog box, 88 Select Remote Folder dialog box, 88 self-healig NTFS, 144 Self-Moitorig, Aalysis, ad Reportig Techology (S.M.A.R.T.), 144 serializatio backups, 252 surrogates, Server Maager, lauchig, 67 servers certificates, 94 clusters, 145 compoets database clusterig, database mirrorig, of log shippig, 191 farms, addig, full server recovery, isns (Iteret Storage Namig Server), 145 log shippig, 192 OS (operatig systems), 49 as recovery targets, 15 SQL aliases, 371 WFE (Web frot-ed), 27, 119, 136 Widows Server 2008 backups, HA (high availability), 117. See also HA (high availability) restorig, Widows Server Backup, 78 eablig, storage, 77 witess, 209, 212 Service Applicatios, 10, 170 catastrophic backups, 244 cofiguratio data, 247 log shippig, 201 services accouts, 234 applicatios, 7, 16, 138 catastrophic backups, 244 Cetral Admiistratio, DNS (Domai Name Services), 19 Excel Services Service Applicatio, 14 IIS (Iteret Iformatio Services), 7 NLB (Widows Network Load Balacig), PerformacePoit Services, 8 restorig, 37, 292 Shared Network Folder optio, 81 shared etwork folders, backups, 82 Shared Service Providers (SSPs), 136 shared storage, moutig, 234 SharePoit Portal Server. See SPS SharePoit_Shell_Access role, 303 sharig files, log shippig, 192 shippig, log, Short Message Service (SMS), 307 ShowTree parameter, 311, 317, 324 Simple Mail Trasfer Protocol. See SMTP simple recovery model, SQL Server 2008 database backups, site collectio, 7, backups, restorig, 296 templates, 394 Site Collectio Backups, sixty-four (64) bit versios of Widows 7, 50 sizig databases, trasactio logs, 191 Small Computer System Iterface. See SCSI S.M.A.R.T. (Self-Moitorig, Aalysis, ad Reportig Techology), 144 SMS (Short Message Service), 307 SMTP (Simple Mail Trasfer Protocol), 19 sap-is, Certificates MMC, 78

438 Idex 421 sapshots database backups, SQL, types of, sockets, SSL (Secure Socket Layer), 61 software liceses, acquirig, 19 load balacig, RAID, spbackup.log files, 252 SPBackupRestoreCosole, spbackup.xml files, 252 spbrtoc.xml file, 249 Specify Destiatio Type page, 81 Specify Remote Shared Folder page, 82 SPGlobalIformatio ode, 252 sprestore.log file, 254 sprestore.xml file, 254 SPS (SharePoit Portal Server), 53 SPSiteCollectio type, 352 SQL (Structured Query Laguage) aliases, 224, 371 sapshots, SQL Server 2005, SQL Server 2005 Express, 151 SQL Server 2008, 44, 151 backups, ew features, restorig, database backups, failover clusters, 39 HA (high availability), See also HA (high availability) liceses, 166 SQL Server 2008 Express, 151 SQL Server 2008 R2, 151 SQL Server 2008 R2 Express, 151 SQL Server Maagemet Studio, 153 SSL (Secure Socket Layer), 61, 403 certificates, 93 95, 114 SSPs (Shared Service Providers), 136 stability best practices, 43 of tools, 47 stadby farms, buildig, startig backups, 85 database mirrorig, 219 Server Maager, 67 states moitorig, 43 recovery, status, restorig, 291 stoppig database mirrorig, 221 storage database clusterig, 233 HA (high availability), 141 locatios, moutig, 234 Widows Server 2008, Widows Server Backup, 77 storage area etworks. See SANs StoragePoit, 167 strategies, 2 3. See also plaig STSADM.exe, 257, subfolders, 90. See also folders success of recoveries, 22 SuGard, 32 support database mirrorig cofiguratios, 209 PowerShell, 121 surrogates, serializatio, suspedig database mirrorig, 221 switches, 8 -UseSqlSapshot, 164 sychroizatio of documets, 404 sychroous operatig mode, database mirrorig, 222 System Ceter Operatios Maager (SCOM), 43, 121 System Properties dialog box, 70 71, 74 systems images, 101, 103 testig, T targets backups, See also backups recovery, determiig, preservig, 37 Tasks Back Up meu optio, 155 TDE (Trasparet Data Ecryptio), 166, 247 TechNet, 92, 257 techical aalysis, 14 techical documets, 20. See also documetatio techical owers, 6 TEMPDB databases, 169 templates, admiistratio, lists, Microsoft SharePoit Desiger 2010, 394 security, sites, 394 Web Applicatios, termiology, 3 6

439 422 SharePoit 2010 Disaster Recovery Guide testig coductig, eviromets, 50 failover clusterig, 237 observig, 30 people, 28 plaig, recovery plas, 98 systems, threads, maagig, Threat Maagemet Gateway. See TMG time, RTOs (recovery time objectives), 4. See also RTOs (recovery time objectives) TMG (Threat Maagemet Gateway), 37, 121 To-Be aalysis, 31 tools, AppCmd.exe, 69, 78 capabilities, determiig, Cluster Admiistrator, 235 Microsoft System Ceter Cofiguratio Maager, 92 Registry Editor, SQL Server Maagemet Studio, 153 trackig chages, 387 recovery progress, 105 traiig, 20, 25 Trasactio Log Backup Settigs dialog box, 194 trasactio logs backups, 161 sizig, 191 Trasactio Log Shippig page, 194 Trasact-SQL (T-SQL), 154 Trasparet Data Ecryptio (TDE), 166 trasport layer security, 403 trust relatioships, 292 T-SQL (Trasact-SQL), 154 types of backups, 64 66, of catastrophic backups, 245 of sapshots, of versioig, U UAG (Uified Access Gateway), 37 UIs (user iterfaces) customizatios, 51 UML (Uified Modelig Laguage), 7 uattached cotet databases, , uatteded service accouts as recovery targets, 15 UNC (uiversal amig covetios) log shippig, 194 recovery images, 102 Uicast mode, Uified Access Gateway. See UAG Uified Modelig Laguage. See UML ulimited use, log shippig, 206 updatig catastrophic backup files, 249 CU (Cumulative Update) packages, 150 usability of tools, 46 usage, determiig, 37 use case, 37 user accouts, 264 user iterfaces. See UIs UseSqlSapshot parameter, 320 -UseSqlSapshot switch, 164 V Validate a Cofiguratio Wizard, 232 validatig compoets, 236 plaig, 30 value of recovery targets, determiig, 26 verifyig certificates, 95 checklists, cotet, 21 preparedess, Versio History dialog box, 386 versios, 20, of OS (operatig systems), 49 VHDs (virtual hard drives), 77 viewig catastrophic backup files, views, Explorer View, virtual hard drives. See VHDs virtualizatio, 41 virtual machies. See VMs virtual servers, amig, 236 VMs (virtual machies), 41 recovery plas, 98 Uicast mode, 122 VMware, 41 Volume Shadow Copy Service. See VSS vsphere, 41 VSS (Volume Shadow Copy Service), 88, 315, vulerability of recovery targets, 26 W walkig, object models, WANs (wide area etworks), 8 backup compressio, 165 database mirrorig, 228 NLB clusters, 131 weakesses, 25

440 Idex 423 Web Applicatios, 7 catastrophic backups, 245 quota templates, Recycle Bi settigs, web.cofig files, 57 WebDAV, Web frot-ed servers. See WFE servers Web Parts, 51 Web Service Applicatios, WFE (Web frot-ed) servers, 27, 47, 119, 136 stadby farms, buildig, 203 Whale, 38 WhatIf parameter, 310, 312, 320, 324, 326 wide area etworks. See WANs Widows Commad Shell, 301 Widow Server 2008 ew features, WidowsImageBackup subfolder, 90 Widows Maagemet Istrumetatio. See WMI Widows Network Load Balacig. See NLB Widows Performace Moitor, 43 Widows Registry backups, exportig, 97 restorig, 115 Widows Server 2008, 49 backups, failover clusterig, full server backups, HA (high availability), 117. See also HA (high availability) idividual compoet backups, restorig, storage, Widows Server Backup, 78 eablig, MMC sap-i, 79 storage, 77 Widows SharePoit Services. See WSS witess servers, 209 cofigurig, 212 database mirrorig, 228 wizards Add Features Wizard, 67 Backup Oce Wizard, 83, Backup Schedule Wizard, 79, 83 Cofigure Database Mirrorig Security Wizard, 212 Recovery Wizard, 106 Validate a Cofiguratio Wizard, 232 WMI (Widows Maagemet Istrumetatio), 121, 307 writers, 359 WSS (Widows SharePoit Services), 53, 152, 167 WSS_ADMIN_WPG security group membership, 304 X Z XML cofiguratio files, 51 yearly cost of disaster recovery, 32 zoes, 7