Noel sps bay_backup_restore

1,166 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,166
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Noel sps bay_backup_restore

  1. 1. Backup and Restore for SharePoint 2010<br />Michael Noel<br />Convergent Computing<br />Twitter: MichaelTNoel<br />
  2. 2. Michael Noel<br /><ul><li>Author of SAMS Publishing titles “SharePoint 2010 Unleashed,” “SharePoint 2007 Unleashed,” “SharePoint 2003 Unleashed”, “Teach Yourself SharePoint 2003 in 10 Minutes,” “Windows Server 2008 R2 Unleashed,” “Exchange Server 2010 Unleashed”, “ISA Server 2006 Unleashed”, and many other titles .
  3. 3. Partner at Convergent Computing (www.cco.com / +1(510)444-5700) – Bay Area based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security</li></li></ul><li>What we will cover<br /><ul><li>What SharePoint Components need to be backed up
  4. 4. Built-in SharePoint Backup Tools
  5. 5. Central Admin Backup
  6. 6. STSADM Backup Methods
  7. 7. SQL Maintenance Jobs
  8. 8. Introduction to System Center Data Protection Manager (DPM) 2010
  9. 9. How Does DPM Work?
  10. 10. In Depth Look at What is Needed to Architect a DPM Environment.</li></li></ul><li>SharePoint Critical Components for Backup<br />
  11. 11. What are the Critical SharePoint 2010 Components?<br /><ul><li>SharePoint Databases
  12. 12. Config Database (typically excluded)
  13. 13. Content Database(s)
  14. 14. Services Databases
  15. 15. IIS Configuration
  16. 16. Web.config files in inetpub directory
  17. 17. Web part assemblies in %systemroot%assembly
  18. 18. Any custom templates</li></li></ul><li>Understanding the SP2010 DatabasesSharePoint 2010 Databases (Part I)<br />
  19. 19. Understanding the SP2010 DatabasesSharePoint 2010 Databases (Part II)<br />
  20. 20. What are the Backup Tools?<br /><ul><li>Two-stage Recycle Bin
  21. 21. SharePoint Central Admin Tool
  22. 22. PowerShell
  23. 23. STSADM
  24. 24. SharePoint Designer
  25. 25. IISBack.vbs
  26. 26. SQL 2005/2008 Tools (Maintenance Plan)
  27. 27. Microsoft System Center Data Protection Manager (DPM) 2007/2010
  28. 28. Third-party (Quest, Metalogix, AvePoint)</li></li></ul><li>Backup with the SharePoint Central Admin Tool<br />
  29. 29. What does the Central Admin Backup Tool do?<br /><ul><li>Full fidelity backups of all SharePoint content and indexes
  30. 30. Backs up all SharePoint databases except Config DB, which is not needed.
  31. 31. Similar to SQL level backup, except can be more granular at the Web Application level
  32. 32. SP2010 now has status indicators
  33. 33. SP2010 now allows for Site Collection Backup from Central Admin</li></li></ul><li>Disadvantages of Central Admin Backup Tool<br /><ul><li>Not automated
  34. 34. If XML catalog is damaged, entire backup can be at risk
  35. 35. No item-level restore capabilities
  36. 36. Not enterprise level</li></li></ul><li>PowerShell Backups<br />
  37. 37. PowerShell Backup in SP2010<br /><ul><li>PowerShell can be used to automate Backups
  38. 38. Backup-SPConfigurationDatabase
  39. 39. Backup-SPFarm
  40. 40. Backup-SPSite
  41. 41. Equivalent to Central Admin or STSADM
  42. 42. Can pipe out results and backup multiple site collections, etc.</li></li></ul><li>STSADM Command Line Backups<br />
  43. 43. STSADM Backup Methods<br /><ul><li>‘Catastrophic’ Backup – command-line version of SharePoint Central Admin Tool
  44. 44. Stsadm –o backup –directory C:BackupFarm –backupmethod FULL
  45. 45. Site Collection Backup – Full fidelity backup of individual Site Collections
  46. 46. Stsadm –o backup –url http://home.companyabc.com/sites/site1 -filename C:BackupSitessite1.bak -overwrite
  47. 47. Sub-Web Export – Partial fidelity export of individual sites, doclibs, and subwebs
  48. 48. Stsadm –o export</li></li></ul><li>STSADM ‘Catastrophic’ Backup<br /><ul><li>Replaces Central Admin Backup, so can be scripted
  49. 49. Used for full farm recovery
  50. 50. Catastrophic Backup/Restore sample syntax:
  51. 51. Stsadm –o backup –directory <directory> </li></ul>-backupmethod <full or differential><br /><ul><li>Stsadm –o restore –directory <directory> </li></ul>-restoremethod <new or overwrite><br />
  52. 52. STSADM Site Collection Backup<br /><ul><li>Full fidelity backup of individual Site Collections to flat files
  53. 53. Enumerates a list of the available sites with the /enumsites option
  54. 54. Can be run multiple times and/or scripted to automate backups
  55. 55. Extremely useful approach to backing up WSS Site collections and personal sites</li></li></ul><li>STSADM Site Collection Backup<br /><ul><li>Example Syntax:
  56. 56. Stsadm.exe –o backup –url http://localhost/sites/marketing -filename C:ackupmarketing.dat
  57. 57. STSADM will backup the entire site collection to a single flat file
  58. 58. Doesn’t scale to very large site collections though</li></li></ul><li>STSADM Site Collection Restore<br /><ul><li>Stsadm.exe –o restore –url http://localhost/sites/marketing -filename C:Backupmarketing.dat -overwrite
  59. 59. Restore over existing Site
  60. 60. Restore to alternate location
  61. 61. Create parallel portal on same server
  62. 62. Restore to different server with certain restrictions</li></li></ul><li>STSADM Sub-Web Exports<br /><ul><li>Partial Fidelity move of specific sets of content (i.e. doclibs, sites, etc.)
  63. 63. Sample syntax:
  64. 64. Stsadm –o export –url http://home.companyabc.com/sites/site1/subsite2 -filename C:ackupExportsubsite2.bak
  65. 65. Stsadm –o import –url http://home.companyabc.com/sites/site1/subsite2 -filename C:ackupExportsubsite2.bak</li></li></ul><li>Internet Information Services Backups<br />
  66. 66. IISBack.VBS Tool<br /><ul><li>Exports out the metaverseconfig of IIS
  67. 67. Should be used before any Virtual Server configuration change or service pack application
  68. 68. Used to restore specific virtual server configuration
  69. 69. Can be scripted</li></li></ul><li>How to backup the IIS Config<br /><ul><li>Run the script using the command line cscript, i.e.:
  70. 70. Cscript c:windowssystem32iisback.vbs /backup /b SPSVSBCK /overwrite
  71. 71. The backup can be copied to a different location, copy all files in the C:Windowssystem32Metaback directory that are named what the backup was (i.e. SPSVSBCK.*)</li></li></ul><li>SQL Maintenance Plan Backups<br />
  72. 72. Backing up using SQL Tools<br /><ul><li>SQL 2005/2008/2008 R2 Management Studio can be used to backup all Databases
  73. 73. Same as Central Admin Backup, but only backs up SQL databases, not index
  74. 74. Can be scheduled as part of a SQL Maintenance Plan
  75. 75. Can backup as Full, Differential, or Incremental
  76. 76. Can backup Config DB, but normally not needed (only supported scenario is during a SAN Snapshot)</li></li></ul><li>SharePoint Designer Exports<br />
  77. 77. SharePoint Designer 2007 Backup and Restore<br /><ul><li>Performs a partial fidelity backup of a SharePoint Site
  78. 78. Some security is lost, such as item level security
  79. 79. Individual elements (such as document libraries, lists, etc) can be exported from the File – Export – Personal Web Package interface.</li></li></ul><li>System Center Data Protection Manager 2010<br />
  80. 80. Features of DPM for SharePoint<br /><ul><li>Item-level recovery of Documents and List Data
  81. 81. VSS Snapshot Integration, can snapshot SQL Databases every 15 minutes
  82. 82. Backup to Disk (near-term), Backup to Tape (long-term) – Direct integration
  83. 83. Not only SharePoint, but File Data, Exchange, SQL, and Bare-metal recovery</li></li></ul><li>DPM Backing up a SharePoint Farm<br />System State<br />Internet InformationServices (IIS)“Front End”<br />SharePoint VSS Writer<br />“Farm” Config dB<br />(SQL)<br />DPM 2007<br />SQL<br />SQL<br />SQL<br />Files<br />Enterprise Search (index)<br />Content Servers (SQL)<br />
  84. 84. Architecting a DPM 2010 Environment for SharePoint<br /><ul><li>64bit Console (Windows Server 2008 or Windows Server 2008 R2)
  85. 85. Single console, no built-in redundancy
  86. 86. Attach large pool of disk to server for near-term backups
  87. 87. Attach supported tape library for long-term backups
  88. 88. Console requires location to store SQL database, can be local SQL Server Express or remote SQL. Critical DB, must be backed up also.
  89. 89. For backups of the console, use a second DPM Server that will backup the first (DPM SRT being retired)</li></li></ul><li>Replica Volumes and Recovery Point Volumes<br /><ul><li>Replica volume required for each ‘unit’ that is being backed up
  90. 90. Recovery Point volume also requierd for each ‘unit’, such as farm
  91. 91. Plan for 3x-4x the amount of space in DPM as exists in SharePoint
  92. 92. Replica volume must be as large as you think the content will grow.
  93. 93. Recovery Point volume must be as the data churn multiplied by the time you keep the data on disk.</li></li></ul><li>DPM Licensing<br /><ul><li>Check with local MS first!
  94. 94. Standard Edition License – One license for each file server or non-application server.
  95. 95. Enterprise Edition License – One for each server that runs the following:
  96. 96. SharePoint (One front-end generally)
  97. 97. SQL (each cluster node requires a license)
  98. 98. Exchange (MB Servers)
  99. 99. Any system that is backed up by the SRT, this may include the DPM Console
  100. 100. Generally cost competitive…
  101. 101. Virtualization Licensing Options…</li></li></ul><li>DPM Agent Installation<br /><ul><li>To protect a farm, DPM needs to install the agent on the following servers
  102. 102. Any Web front end server(that is used to invoke the writer) This can be a dedicated server in larger farms.
  103. 103. The Index Server(s)
  104. 104. All back end SQL servers
  105. 105. After agent installation, run ‘Configuresharepoint.exe –EnableSharePointProtection’ on SP Server from DPM Server directory</li></li></ul><li>DPM Protection – Key Features<br /><ul><li>DPM protects the entire farm data by a single check box
  106. 106. DPM leverages the WSS writer to determine all the components to back up
  107. 107. At the time of backup, DPM works across multiple servers in the farm and backs up the data from across all these servers
  108. 108. DPM only performs express full backups for SharePoint
  109. 109. After the backup is done, DPM queries the SharePoint object model to get all the information about the sites, items, etc.
  110. 110. DPM 2010 does not require Recovery Farm!</li></li></ul><li>SharePoint Recovery<br />The Entire Farm<br />“Farm” Config dB<br />(SQL)<br />Entire Farm<br />DPM 2007<br />Enterprise Search (index)<br />Content Servers (SQL)<br />
  111. 111. SharePoint Recovery<br />The Entire Farm<br />A Content DB<br />“Farm” Config dB<br />(SQL)<br />Content DB information<br />DPM 2007<br />Content DB<br />Enterprise Search (index)<br />Content Servers (SQL)<br />
  112. 112. SharePoint Recovery<br />The Entire Farm<br />A Content DB<br />Site Collection<br />A Site<br />Document<br />Site Collection / Site / Individual Document<br />“Farm” Config dB<br />(SQL)<br />DPM 2007<br />DPM handles restore thru Recovery Farm to production Farm<br />Farm then redirects data to appropriate content database and site<br />Enterprise Search (index)<br />Content Servers (SQL)<br />
  113. 113. Key Benefits of DPM 2010<br /><ul><li>Near zero data loss for Exchange Server, SQL Server,and SharePoint Server
  114. 114. Seamless disk-to-disk-to-tape for backups
  115. 115. Recoveries within minutes instead of hours
  116. 116. Unified policy allows protection of multiple data types to any media – in one schedule and with common tuning options
  117. 117. Eliminate the backup window of your production servers
  118. 118. Shrink potential data loss down to 15 minutes
  119. 119. Application recovery direct from backup UI – no pre-staging
  120. 120. Enable end-users to perform their own recoveries (file servers only)
  121. 121. Remove tapes from branch officesand centralize backups at the datacenter
  122. 122. Better Admin in 2010 (Auto Consistency checks, auto resizing of volumes</li></li></ul><li>Demo<br />Taking a look at DPM 2010 for SharePoint 2010 Backup<br />
  123. 123. Third-party Backup Solutions<br /><ul><li>Metalogix Selective Restore Manager
  124. 124. Quest Recovery Manager for SharePoint
  125. 125. DocAveAvePoint Backup for Microsoft Office SharePoint Products and Technologies
  126. 126. Commvault Galaxy Data Protection
  127. 127. Symantec Backup Exec/NetBackup
  128. 128. Many others…
  129. 129. Provide for item-level recovery and complex DR scenarios</li></li></ul><li>Session Summary<br /><ul><li>Examine existing tools to backup and restore SharePoint, but understand their limitations.
  130. 130. Use STSADM Site Collection backup if needing to move Site Collections between farms
  131. 131. Consider the use of DPM 2010 for item level recovery and snapshot capabilities</li></li></ul><li>Please complete the session survey<br />Thank You!<br />
  132. 132. Thank You To Our Sponsors!<br />
  133. 133. Thanks for attending!Questions?<br />Michael Noel<br />Twitter: @MichaelTNoel<br />www.cco.com<br />

×