Techedafricademystifyingbackuprestoreinsharepoint2007 090805103250 Phpapp02
- 2. Demystifying Backup and Restore for SharePointJoel OlesonSr. Analyst@joelolesonQuest SoftwareSession Code:
- 3. Who is SharePoint Joel?8 year SharePoint Veteran…First SharePoint AdminSr. Architect – SharePoint at Quest softwareTop IT SharePoint BlogBlog: http://www.sharepointjoel.comTwitter: @joeloleson
- 4. AgendaUnderstanding the problemDefining requirementsDiscuss backup & recovery solutionsTips & Tricks – Addressing gaps in backup/restoreSummary and Q&A(Compliments to Mike Watson)
- 5. The problemWhy is SharePoint Protection Difficult?
- 6. Why SharePoint Data Protection is DifficultSharePoint is confusing
- 7. Multiple servers with different roles
- 10. Configurations
- 11. Logical architecture doesn’t translate into physical componentsWhy SharePoint Data Protection is DifficultCompeting goals require different solutions:Item level recovery Disaster RecoveryHigh AvailabilityMany solutions available. Not obvious what to use:SharePoint Native BackupSharePoint Designer Recycle BinSQL backupDPMThird-party solutions
- 12. What in Your SharePoint Environment Needs Protection?Do you need to protect all of your farms, servers, services, customizations, and configurations?
- 13. What do you need to backupYour DatabasesAll Configuration and settingsYour Services (Index)External Code and Dev assets
- 15. The planPolicy Driven Backup and Recovery
- 16. Creating a Backup/Recovery SolutionDifficult but not impossible!What needs to be protected from what scenarios?How likely are those scenarios?How much data loss can be tolerated?How quickly must items/environment be restored?Test and price potential solutions.Mitigate issues.Choose and communicate solution.
- 18. Protected From What Scenarios?
- 19. How SLA Affects Your Recovery Plan
- 20. Recycle Bin with 2 levels of recoveryEnd-user targeted with access from the site itselfSite Administrator (at the Site Collection) accessible at the second levelTurned on by default through Central AdminConfigured at the Web Application LevelThe No Brainer…
- 21. RTO/RPO – Very Important!How much data loss can be tolerated?How quickly must data/environment be restored?RTO/RPO affect:The technologies you chooseThe strategies you deployThe simplicity/complexity of your solutionThe location of your backups and environments
- 22. How the "Nines" Relate to Yearly Downtime
- 23. Backup/Recovery solutionsTest & Price Potential Solutions
- 24. Protecting ContentIt’s nearly all about the Content Database!
- 25. Content Database ProtectionSimple Problem – Difficult SolutionEndless options:SharePoint native backupSQL Native backup With compression?Simple or Full recovery model?Full, Differential, Incremental backups?Transaction log backups?What to store and how long?SQL log shipping, mirroring, replication?DPM?Third-Party backup and replication tools?
- 26. Content Database RecoveryEven more difficult!SQL database recovery workflowConfirm itemConfirm locationTrack down database backup timelineRecover backups (online or offline (tape))Position backups (same server/farm, recovery farm)Confirm backups are validRestore backupsAttach backups to SharePointConfirm item is availableRetrieve item and position for end userRecover to original farmRecover to a restore farmExtract data from SQL.Bring DR database online.
- 27. “I’m planning on using SharePoint’s Native Backup Restore, are there any considerations I should know?SharePoint Native Backup/RestoreSharePoint Native Backup/Restore provides an out of the box base solutionSharePoint’s Native Backup/Restore is only recommended for Small to Medium Sized Deployments…
- 28. STSADM for Operations and ScriptingTool for the right job…To create a farm backup:Use stsadm –o backup -directoryTo migrate a site collection:Use stsadm –o backup http://server/site (no directory)To migrate a site:Use stsadm –o export/import for sitesTo migrate a list: Access or Excel or Third party tool (watch creator/created date)
- 29. Characteristics of a Small to Medium-Size Deployment (Data Perspective)Site Collections No Larger than 12-15 GB*Content Databases No Larger than 100 GB*Deployed in up to three tiers, on no more than five servers (one to three front-end Web servers, one application server, and one computer or cluster running Microsoft SQL Server.)**Source: Whitepaper “Data protection and recovery for Office SharePoint Server in small to medium deployments”
- 30. SharePoint 2007 Native Backup & RestoreOut of the Box User Interface via Central AdministrationCommand line access via STSADM tool‘Hooks up’ SharePoint Databases and Search index on RestoreSupports Full and Differential Backups*Easy to UseBackup/Restore at Farm or Web Application LevelThe only way native way to backup/restore the Search index
- 31. How Native SharePoint Backup WorksFarmCentral Admin UI or ConsoleFile ServerSQL Backup/Restore
- 32. SharePoint 2007 Native Backup/RestoreWhat’s Missing???Does not Provide Scheduling Functionality in SharePoint (Use Windows Task Scheduler)Does not Backup any Configurations/Customizations to any files in the “12 Hive” or Web.config filesDoes not Backup IIS Settings/ConfigurationsDoes not Backup Alternate Access Mappings (AAM)Cannot Backup Directly to Tape (only to UNC)
- 33. SQL-Only Backup/Restore“My SQL servers are managed by a separate organization or data center from my SharePoint installations…” “I prefer SQL Server Backups for Performance and Availability…”Advantages & Benefits:Existing SQL Server disaster recovery strategies can be re-usedCan provider substantially faster Backup/Restore than MOSS 2007’s Native Backup/RestoreCan leverage 3rd party tools such as LiteSpeed for SQL Server to improve Backup/Restore Performance Provides a full-fidelity data backup
- 34. SQL-Only Backup/RestoreConsiderations & Disadvantages:Does not Backup any WFE Configurations or SolutionsRequires Admin to Manually Reattach Content Databases to the Web applications After a RecoveryManually Backup / Restore all customizations on WFE Servers (.Net Assemblies, Features, IIS Metabase, etc. – batch file can help automate this process)No need to Backup Search Database (As it can’t be synchronized with Search Index)Recommend Backup/Restore of SSP separately via SharePoint Native Backup & Restore
- 35. Why Backup/Restore is Not Highly Available or DRSimply not fast enoughRate of restore * content size = RTO Example:100MB/sec * 5TB > 14 hoursComplicated recovery procedureProne to errorSome important configurations will likely be lost.
- 36. Failover SQL Mirroring 2 Farms
- 37. Mirroring Within Farm< 1ms latency>LAN speed
- 38. Third Party SolutionsThere are three main categories:Storage Solutions – Replication of content on disk to another storage set or system.Backup/Restore – Integrate with SQL, file system, or VSS to provide backup/restore functionality.Caching/Synchronization – Use a variety of methods to cache content to a remote store or replicate content across sites/farms.
- 39. Quick Note on the Infrastructure UpdateInfrastructure update includes some major HA/DR improvementsOverall improvement in stability/perf (better stored procs)Faster patching reduces downtime.VSS Writer enhancements improve reliability.Full crawls no longer necessary after DB attach:Content DB’s do not get assigned new GUID’s !!!!Change log remains intact. http://support.microsoft.com/kb/953750
- 40. Tips and tricks Mitigating problems with backup/restore solutions
- 41. Improving Performance of Native BackupCo locate the backup share with the largest backup components.Ensure the index disk has good read performance. (100MB/sec or better)Ensure the backup LUN has good write performance. (100MB/sec or better) Ensure database LUN(s) have good read performance. (150MB/sec or better)Ensure Gbps connectivity between remote components and backup share. (1Gbps or 100MB/sec)Ensure all crawls (including anchor text) are stopped/paused.
- 42. Using A SQL Connection Alias with SharePoint1. SharePoint configured to use SQL1 as default SQL server2. Connection Alias defined: SQL1 = SQL13. Upon failover. Connection Alias updated: SQL1 = SQL2SQL1SQL2
- 43. Prevent Database RestoresUse granular protection solutions instead.Recycle binList item versioningPublishing (page versioning)Quick Recovery Tool (like Quest)Gaps exist.No site or web recycle bin. Use the MSIT Site Delete capture tool http://www.codeplex.com/governance/Release/ProjectReleases.aspx?ReleaseId=14351No centralized control over item and page versioning
- 44. Use Solutions!Roll up customizations as solution packagesRoll up as many customizations into a single package as possible.Solutions provide automatic deployment, simplified management, upgrade, and HA/DR efficiencies.Store solutions offsite (and on standby farm) with installation instructions.Build roll up packages on a regular basis.
- 45. DEMO: Quest Recovery ManagerProvides granular and scalable recovery of anything in the backup of your SharePoint 2003 and 2007 content database
- 46. SharePoint 2010 sneak Peak Video Demo – Backup/Recovery
- 47. Sneak Peak Video: SharePointFilter out noise video
- 48. SharePoint 2010 sneak PeakSneak Peak Videos: http://sharepoint.microsoft.com/2010/Sneak_Peek/
- 49. SummarySharePoint Backup/Recovery is tricky, but not impossible.Traditional backup/restore is not HA or DR. Different requirements sometimes require different solutions. Most solutions have issues. Look around for innovative fixes. No one solutions meets all needs. Combine solutions when necessary.
- 50. SharePointForAll.comAggregation of Quest SharePoint Team FeedsUnique IT ContentMigrationDisaster Recovery/BackupProduct Update Drilldown and Webcast AnnouncementsBeta access to new SharePoint tools and products!DropThisReorg WizardAND MORE!!!Quest SharePoint tools discussion forums
- 51. Watch Out for Killer Bunnies
- 52. Quest Solutions for SharePoint Site Administrator for SharePoint Discover, understand and manage your SharePoint environmentQuest SQL Server Solutions Maximize SQL Server performance while simplifying tasks and providing visibility and controlQuest Web Parts Enable rapid development of SharePoint applicationsRecovery Manager for SharePointGranular SharePoint recovery for enterprise-level needsMigration Manager for SharePoint SharePoint 2003 to 2007 migrationFile Migrator for SharePoint File shares to SharePoint migrationPublic Folder Migrator for SharePointExchange Public Folders to SharePoint migrationNotes Migrator for SharePointNotes application content to SharePoint migration48
- 53. Required Slide10 pairs of MP3 sunglasses to be wonComplete a session evaluation and enter to win!
- 54. Thank You!
- 55. Required Slide© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
- 56. Required SlideSpeakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings from Tech-Ed website. These will only be available after the event.Tech·Ed Africa 2009 sessions will be made available for download the week after the event from: www.tech-ed.co.zawww.microsoft.com/techedInternational Content & Communitywww.microsoft.com/learningMicrosoft Certification & Training Resourceshttp://microsoft.com/technetResources for IT Professionalshttp://microsoft.com/msdnResources for DevelopersResources
Editor's Notes
- #33: An example of a warm standby environment utilizing a second SharePoint farm deployed in a secondary data center using SQL Server High Performance Mirroring to replicate only the content databases. During a failover, the content databases are brought online and attached to the existing farm.
- #34: An example of a straddle farm installed in two closely located data centers. In this example SQL High Availability Mirroring is used to replicate all SharePoint farm databases to a standby SQL server (mirror). The network conditions between the two datacenters allow high throughput and remains supportable. A load balancer solution or DNS directs clients to the active data center.