AUSPC 2013 - Business Continuity Management in SharePoint


Published on

Providing for a highly available and disaster-tolerant SharePoint environment is no small task; as there are multiple components that require backup, and various architectural design options that each provide for various degrees of business continuity. Consequently, understanding how to design and implement a BCM solution for SharePoint is a must. This session covers BCM for SharePoint, including a thorough discussion of SharePoint Backup and Restore options, a discussion of various BCM-related architectural designs, and a frank look at some of the new SQL 2012 AlwaysOn options for SharePoint.

Published in: Technology
  • 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

No notes for slide

AUSPC 2013 - Business Continuity Management in SharePoint

  1. 1. Michael Noel, CCO
  2. 2. Thank you to our sponsors
  3. 3. Great to be back in Beautiful Australia!
  4. 4. • What are the critical SharePoint components tobackup?• SharePoint Tools available for backup• Tools and Scenarios Breakdown• SharePoint Central Admin Tool• PowerShell Backups• IIS Backups• SQL Backups• Third Party / DPM• SQL Backup and Restore Scenarios in Depth• SQL AlwaysOn Availability Groups• SQL AOAGs for Aggressive SLAs• Supportability of various AOAG models within SharePoint DBs
  5. 5. Business Continuity Managementin SharePoint 20135
  6. 6. • SharePoint Databases• Content Database(s)• Service Application Databases• Config Database (typically) excluded• IIS Configuration• Web.config files in inetpub directory• Web part assemblies in %systemroot%assembly• Any custom templates
  7. 7. Business Continuity Managementin SharePoint 20137
  8. 8. Tool Restorable Objects MaximumBackup SizeSupportedSupportedBackupTypeSPCA/PowerShell FarmBackup/Restore• Farm• Search• Service• Web Application• Content Database• Sit Collection• Site• List item/document• Configurations• Solutions< 200 GB FullIncrementalSQL Server • Content Database• Site (Single Site Collectionin a DB)• List item/document> 200 GBrequireadditionalmgmt, butsupportedFullDifferentialSite CollectionBackup/Restore• Site Collection (no biggerthan 80-100GB)100GB FullImport/Export • Site (List or Doc Library)• List Items• Solutions100GB Full
  9. 9. Scope Backup RestoreCompleteFarmRegular backup schedules needed tohelp protect data and address disasterrecovery, farm failure, or test backupprocessDisaster recovery – recreate acomplete SharePoint farm on newhardware, or in a different location,or test your backup and recoveryvaliditySiteCollection,Site or ListPeriodic backup schedules needed forattached or unattached read-onlysites, site collections, or listsRestore content – use unattacheddatabases to restore outdated sitecollections, sites, or databasesContentDatabaseRegular backup schedules needed ascontent databases can grow to bevery large and helps reduce datalosses that can occur from hardwarefailure or power outagesRestore content database – to anew location on a farmServiceApplicationsRegular backup schedules needed tomake sure all configurations and datathat are related to service applicationare available for recoveryRestore service applications –situations sometime arise that aspecific service application must berestored instead of the completefarmCompleteFarmDatabaseRegular backup schedules forconfiguration, Central Administrationcontent, content, and serviceapplication databases provide aneasier process when employing newdatabase serversMove complete farm – newdatabase server(hardware/software) brought onlineto replace an old one
  10. 10. Business Continuity Managementin SharePoint 201310
  11. 11. • Full fidelity backups of all SharePoint content andindexes• Backs up all SharePoint databases except Config DB,which is not needed.• Similar to SQL level backup, except can be moregranular at the Web Application level• SP2013 has status indicators• SP2013 allows for Site Collection Backup from CentralAdmin
  12. 12. • Not automated• If XML catalog is damaged, entirebackup can be at risk• No item-level restore capabilities• Not enterprise level
  13. 13. Business Continuity Managementin SharePoint 201313
  14. 14. • PowerShell can be used to automateBackups• Backup-SPConfigurationDatabase• Backup-SPFarm• Backup-SPSite• Equivalent to Central Admin Backups• Can pipe out results and backupmultiple site collections, etc.
  15. 15. Cmdlet SharePoint ComponentBackup-SPFarm Entire FarmService ApplicationsWeb ApplicationsContent DatabasesRestore-SPFarm Entire FarmFarm Configuration OnlyService ApplicationsWeb ApplcationsContent DatabasesBackup-SPConfigurationDatabase Farm Configuration OnlyBackup-SPSite / Restore-SPSite Site CollectionExport-SPWeb / Import-SPWeb SitesSubsitesLibrariesLists
  16. 16. • Farm Configuration Only Backup• backup-spfarm –backupMethod full –directory servernameSP2010Backup -configurationonly• Complete Farm Backup• Backup-spfarm –backupmethod full –directory servernameSP2010Backup• Backup-SPFarm specific parameters• -BackupMethod• -BackupThreads
  17. 17. • Configuration Database Backup• Backup-spconfigurationdatabase –directoryservernamesp2010backup –databaseserverserver –databasename mss_configdb• Backup Farm Configuration Information• Information Rights Management• Workflow• Diagnostic logging• Customizations [solutions deployed]• Outbound e-mail configuration• Antivirus settings
  18. 18. • Backup Site Collection• Backup-SPSite –Identity -Pathservernamesp2010backupdemosc.bak -Force• Other Parameters –• -NoSiteLock – use with caution, possible data corruption• -UseSQLSnapshot – use content database snapshot whendoing a backup• Can be run multiple times and/or scripted toautomate backups• Extremely useful approach to backing up WSS Sitecollections and personal sites
  19. 19. • Granular Backup/Restore From CentralAdministration• Site Collection Backup• Export a site or list• Recover data from an unattached content database• Granular Backup Job Status indicators• Granular restore operations only usingPowerShell• Workflows are not included whenexporting a site or a list
  20. 20. • Export-SPWeb –Identity -pathserversp2010backupsfeaturelist.bak -itemurl “features” –force• Option to include user security andversions
  21. 21. • Granular restores of SharePoint content• Read-only content databases• Restored SharePoint content databases• Content database snapshots• Restore Site Collections, Sites, Librariesand Lists
  22. 22. Business Continuity Managementin SharePoint 201322
  23. 23. • Open a command prompt by using theRun as Administrator option and changedirectory to %windir%system32inetsrv.• At the command prompt, type appcmdadd backup <backupname>. If you donot include the name of the backup, thesystem will name it for you by using adate, time format.
  24. 24. Business Continuity Managementin SharePoint 201324
  25. 25. • SQL 2008 R2/SQL 2012 Management Studio canbe used to backup all Databases• Same as Central Admin Backup, but only backs upSQL databases, not index or configuration• Can be scheduled as part of a SQL MaintenancePlan• Can backup as Full, Differential, Incremental, orTransaction Log• Can backup Config DB, but normally not needed(only supported scenario is during a SANSnapshot)
  26. 26. • Any DB in FULL recovery mode (most ofSharePoint DBs are in FULL by default)will continue to grow logs indefinitely• Be sure to run a full backup, then atransaction log backup from SQL. Thiswill clear out logs but not shrink them• To shrink, you need to also run DBCCSHRINKFILE after the backups
  27. 27. USE SPF1_ConfigDB;BACKUP DATABASE SPF1_ConfigDB TODISK=NUL:;BACKUP LOG SPF1_ConfigDB TO DISK=NUL:;DBCC SHRINKFILE(SPF1_ConfigDB_log,1000)• NOTE: This sample backs up to NULL,which effectively means it‟s only flushingthe logs. Replace NULL with the backuplocation for your environment
  28. 28. Business Continuity Managementin SharePoint 201328
  29. 29. • Microsoft snapshot-based backup and restore tool• Directly supports backup and restore of aSharePoint farm (Replaces the need forSPCA/PowerShell options)• Point to farm member, backs up config of allservers in farm• Supports very large database (200GB+)
  30. 30. • Multiple tools available• Provide for item-level recovery and complex DRscenarios• Often „fix‟ issues associated with native SharePointbackup and backup all components at once• Major vendors have tools (Check vendor hall here)
  31. 31. Business Continuity Managementin SharePoint 201331
  32. 32. Business Continuity Managementin SharePoint 201347
  33. 33. • Two distinct technologies that share the samename• AlwaysOn Failover Clustering is a different thing!• A Failover Cluster Instance (FCI) uses traditional SharedStorage Clustering (one copy of data shared by multiplenodes)• Same marketing name, but completely differenttechnology• AlwaysOn Availability Groups correspond to thenew version of SQL Database Mirroring – HighAvailability and Disaster Recovery at the Data Tier
  34. 34. High Availability and DisasterRecoverySQL Server SolutionPotentialData Loss(RPO)PotentialRecoveryTime (RTO)AutomaticFailoverReadableSecondariesAlwaysOn Availability Group - synchronous-commitZero Seconds Yes 0 - 2AlwaysOn Availability Group - asynchronous-commitSeconds Minutes No 0 - 4AlwaysOn Failover Cluster Instance NA Seconds-to-minutesYes NADatabase Mirroring - High-safety (sync + witness) Zero Seconds Yes NADatabase Mirroring - High-performance (async) Seconds Minutes No NALog Shipping Minutes Minutes-to-hoursNo Not duringa restoreBackup, Copy, Restore Hours Hours-to-daysNo Not duringa restore
  35. 35. PossibleDeploymentScenarioslisted – Notethat ContentDBs can beSync andAsync, S.A.DBs onlySync
  36. 36. • Windows Server 2008 R2 w SP1 or WindowsServer 2012 – Enterprise Edition• One per node• Can use Virtualization licensing options• SQL Server 2012 Enterprise Edition• MS has moved to „Oracle model‟ of licensing,based on CPU power• Legacy licenses of SQL Enterprise Edition canbe „grandfathered in‟ if you have upgradeassurance
  37. 37. • (Asymmetric Storage)• (Node Weight Fix)• (SCSI Device TestFailure)• (Unneded Reg KeyChange Notifications)• (Net 35 Always OnFeatures)• (IPSecConnectionDelay) - Not needed if you aren‟t using IPSec• (IPv6 Long Failover) -Not needed if you aren‟t using IPv6• (Slow Failover withNo Router) – Not needed in most scenarios, review todetermine if it applies to you
  38. 38. • Examine existing tools to backup and restoreSharePoint, but understand their limitations.• Be sure to backup all aspects of a SharePoint farm• Test your restore on a regular basis• Consider the use of DPM or third party for itemlevel recovery and snapshot capabilities• Consider the use of SQL AOAGs to allow for bothHA and DR of SharePoint data
  39. 39. Michael NoelCompany Site: http://www.cco.comTwitter: blog:
  40. 40. Thank you to our sponsors