Your SlideShare is downloading. ×
Noel sps bay_backup_restore
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Noel sps bay_backup_restore


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


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