1. Backup and Restore for SharePoint 2010 Michael Noel Convergent Computing Twitter: MichaelTNoel

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?

12. Config Database (typically excluded)

13. Content Database(s)

14. Services Databases

15. IIS Configuration

16. Web.config files in netpub directory

17. Web part assemblies in %systemroot%ssembly

19. Understanding the SP2010 DatabasesSharePoint 2010 Databases (Part II)

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

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

34. If XML catalog is damaged, entire backup can be at risk

35. No item-level restore capabilities

38. Backup-SPConfigurationDatabase

39. Backup-SPFarm

40. Backup-SPSite

41. Equivalent to Central Admin or STSADM

44. Stsadm –o backup –directory C:ackuparm –backupmethod FULL

45. Site Collection Backup – Full fidelity backup of individual Site Collections

46. Stsadm –o backup –url http://home.companyabc.com/sites/site1 -filename C:ackupitesite1.bak -overwrite

47. Sub-Web Export – Partial fidelity export of individual sites, doclibs, and subwebs

49. Used for full farm recovery

50. Catastrophic Backup/Restore sample syntax:

53. Enumerates a list of the available sites with the /enumsites option

54. Can be run multiple times and/or scripted to automate backups

56. Stsadm.exe –o backup –url http://localhost/sites/marketing -filename C:ackuparketing.dat

57. STSADM will backup the entire site collection to a single flat file

59. Restore over existing Site

60. Restore to alternate location

61. Create parallel portal on same server

63. Sample syntax:

64. Stsadm –o export –url http://home.companyabc.com/sites/site1/subsite2 -filename C:ackupxportubsite2.bak

67. Should be used before any Virtual Server configuration change or service pack application

68. Used to restore specific virtual server configuration

70. Cscript c:indowsystem32isback.vbs /backup /b SPSVSBCK /overwrite

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

78. Some security is lost, such as item level security

81. VSS Snapshot Integration, can snapshot SQL Databases every 15 minutes

82. Backup to Disk (near-term), Backup to Tape (long-term) – Direct integration

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.

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.

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…

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

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.

111. SharePoint Recovery The Entire Farm A Content DB “Farm” Config dB (SQL) 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 Document Site Collection / Site / Individual Document “Farm” Config dB (SQL) 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)

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

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…

130. Use STSADM Site Collection backup if needing to move Site Collections between farms

132. Thank You To Our Sponsors!

133. Thanks for attending!Questions? Michael Noel Twitter: @MichaelTNoel www.cco.com