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.

1. Michael Noel, CCO

2. Thank you to our sponsors

3. Great to be back in Beautiful Australia!

4. • What are the critical SharePoint components to
backup?
• 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. Business Continuity Management
in SharePoint 2013
5

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. Business Continuity Management
in SharePoint 2013
7

8. Tool Restorable Objects Maximum
Backup Size
Supported
Supported
Backup
Type
SPCA/PowerShell Farm
Backup/Restore
• Farm
• Search
• Service
• Web Application
• Content Database
• Sit Collection
• Site
• List item/document
• Configurations
• Solutions
< 200 GB Full
Incremental
SQL Server • Content Database
• Site (Single Site Collection
in a DB)
• List item/document
> 200 GB
require
additional
mgmt, but
supported
Full
Differential
Site Collection
Backup/Restore
• Site Collection (no bigger
than 80-100GB)
100GB Full
Import/Export • Site (List or Doc Library)
• List Items
• Solutions
100GB Full

9. Scope Backup Restore
Complete
Farm
Regular backup schedules needed to
help protect data and address disaster
recovery, farm failure, or test backup
process
Disaster recovery – recreate a
complete SharePoint farm on new
hardware, or in a different location,
or test your backup and recovery
validity
Site
Collection,
Site or List
Periodic backup schedules needed for
attached or unattached read-only
sites, site collections, or lists
Restore content – use unattached
databases to restore outdated site
collections, sites, or databases
Content
Database
Regular backup schedules needed as
content databases can grow to be
very large and helps reduce data
losses that can occur from hardware
failure or power outages
Restore content database – to a
new location on a farm
Service
Applications
Regular backup schedules needed to
make sure all configurations and data
that are related to service application
are available for recovery
Restore service applications –
situations sometime arise that a
specific service application must be
restored instead of the complete
farm
Complete
Farm
Database
Regular backup schedules for
configuration, Central Administration
content, content, and service
application databases provide an
easier process when employing new
database servers
Move complete farm – new
database server
(hardware/software) brought online
to replace an old one

10. Business Continuity Management
in SharePoint 2013
10

11. • Full fidelity backups of all SharePoint content and
indexes
• Backs up all SharePoint databases except Config DB,
which is not needed.
• Similar to SQL level backup, except can be more
granular at the Web Application level
• SP2013 has status indicators
• SP2013 allows for Site Collection Backup from Central
Admin

12. • Not automated
• If XML catalog is damaged, entire
backup can be at risk
• No item-level restore capabilities
• Not enterprise level

13. Business Continuity Management
in SharePoint 2013
13

14. • PowerShell can be used to automate
Backups
• Backup-SPConfigurationDatabase
• Backup-SPFarm
• Backup-SPSite
• Equivalent to Central Admin Backups
• Can pipe out results and backup
multiple site collections, etc.

15. Cmdlet SharePoint Component
Backup-SPFarm Entire Farm
Service Applications
Web Applications
Content Databases
Restore-SPFarm Entire Farm
Farm Configuration Only
Service Applications
Web Applcations
Content Databases
Backup-SPConfigurationDatabase Farm Configuration Only
Backup-SPSite / Restore-SPSite Site Collection
Export-SPWeb / Import-SPWeb Sites
Subsites
Libraries
Lists

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. • Configuration Database Backup
• Backup-spconfigurationdatabase –directory
servernamesp2010backup –databaseserver
server –databasename mss_configdb
• Backup Farm Configuration Information
• Information Rights Management
• Workflow
• Diagnostic logging
• Customizations [solutions deployed]
• Outbound e-mail configuration
• Antivirus settings

18. • Backup Site Collection
• Backup-SPSite –Identity
http://justsharepoint.com/Sites/demo -Path
servernamesp2010backupdemosc.bak -Force
• Other Parameters –
• -NoSiteLock – use with caution, possible data corruption
• -UseSQLSnapshot – use content database snapshot when
doing a backup
• Can be run multiple times and/or scripted to
automate backups
• Extremely useful approach to backing up WSS Site
collections and personal sites

19. • Granular Backup/Restore From Central
Administration
• Site Collection Backup
• Export a site or list
• Recover data from an unattached content database
• Granular Backup Job Status indicators
• Granular restore operations only using
PowerShell
• Workflows are not included when
exporting a site or a list

20. • Export-SPWeb –Identity
http://justsharepoint.com/sites/dem
o/ -path
serversp2010backupsfeaturelist.b
ak -itemurl “features” –force
• Option to include user security and
versions

21. • Granular restores of SharePoint content
• Read-only content databases
• Restored SharePoint content databases
• Content database snapshots
• Restore Site Collections, Sites, Libraries
and Lists

22. Business Continuity Management
in SharePoint 2013
22

23. • Open a command prompt by using the
Run as Administrator option and change
directory to %windir%system32inetsrv.
• At the command prompt, type appcmd
add backup <backupname>. If you do
not include the name of the backup, the
system will name it for you by using a
date, time format.

24. Business Continuity Management
in SharePoint 2013
24

25. • SQL 2008 R2/SQL 2012 Management Studio can
be used to backup all Databases
• Same as Central Admin Backup, but only backs up
SQL databases, not index or configuration
• Can be scheduled as part of a SQL Maintenance
Plan
• Can backup as Full, Differential, Incremental, or
Transaction Log
• Can backup Config DB, but normally not needed
(only supported scenario is during a SAN
Snapshot)

26. • Any DB in FULL recovery mode (most of
SharePoint DBs are in FULL by default)
will continue to grow logs indefinitely
• Be sure to run a full backup, then a
transaction log backup from SQL. This
will clear out logs but not shrink them
• To shrink, you need to also run DBCC
SHRINKFILE after the backups

27. USE SPF1_ConfigDB;
BACKUP DATABASE SPF1_ConfigDB TO
DISK='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 flushing
the logs. Replace NULL with the backup
location for your environment

28. Business Continuity Management
in SharePoint 2013
28

29. • Microsoft snapshot-based backup and restore
tool
• Directly supports backup and restore of a
SharePoint farm (Replaces the need for
SPCA/PowerShell options)
• Point to farm member, backs up config of all
servers in farm
• Supports very large database (200GB+)

30. • Multiple tools available
• Provide for item-level recovery and complex DR
scenarios
• Often ‘fix’ issues associated with native SharePoint
backup and backup all components at once
• Major vendors have tools (Check vendor hall here)

31. Business Continuity Management
in SharePoint 2013
31

47. Business Continuity Management
in SharePoint 2013
47

48. • Two distinct technologies that share the same
name
• AlwaysOn Failover Clustering is a different thing!
• A Failover Cluster Instance (FCI) uses traditional Shared
Storage Clustering (one copy of data shared by multiple
nodes)
• Same marketing name, but completely different
technology
• AlwaysOn Availability Groups correspond to the
new version of SQL Database Mirroring – High
Availability and Disaster Recovery at the Data Tier

49. High Availability and Disaster
Recovery
SQL Server Solution
Potential
Data Loss
(RPO)
Potential
Recovery
Time (RTO)
Automatic
Failover
Readable
Secondaries
AlwaysOn Availability Group - synchronous-
commit
Zero Seconds Yes 0 - 2
AlwaysOn Availability Group - asynchronous-
commit
Seconds Minutes No 0 - 4
AlwaysOn Failover Cluster Instance NA Seconds
-to-minutes
Yes NA
Database Mirroring - High-safety (sync + witness) Zero Seconds Yes NA
Database Mirroring - High-performance (async) Seconds Minutes No NA
Log Shipping Minutes Minutes
-to-hours
No Not during
a restore
Backup, Copy, Restore Hours Hours
-to-days
No Not during
a restore

50. Possible
Deployment
Scenarios
listed – Note
that Content
DBs can be
Sync and
Async, S.A.
DBs only
Sync

51. • Windows Server 2008 R2 w SP1 or Windows
Server 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 can
be ‘grandfathered in’ if you have upgrade
assurance

52. • http://support.microsoft.com/kb/976097 (Asymmetric Storage)
• http://support.microsoft.com/kb/2494036 (Node Weight Fix)
• http://support.microsoft.com/kb/2531907 (SCSI Device Test
Failure)
• http://support.microsoft.com/kb/2616514 (Unneded Reg Key
Change Notifications)
• http://support.microsoft.com/kb/2654347 (Net 35 Always On
Features)
• http://support.microsoft.com/kb/980915 (IPSecConnection
Delay) - Not needed if you aren’t using IPSec
• http://support.microsoft.com/kb/2578113 (IPv6 Long Failover) -
Not needed if you aren’t using IPv6
• http://support.microsoft.com/kb/2582281 (Slow Failover with
No Router) – Not needed in most scenarios, review to
determine if it applies to you

53. • Examine existing tools to backup and restore
SharePoint, 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 item
level recovery and snapshot capabilities
• Consider the use of SQL AOAGs to allow for both
HA and DR of SharePoint data

54. Michael Noel
Company Site: http://www.cco.com
Twitter: http://twitter.com/michaeltnoel
LinkedIn: http://linkedin.com/in/michaeltnoel
Facebook: http://facebook.com/michaelnoel
Slides: http://slideshare.net/michaeltnoel
Travel blog: http://sharingtheglobe.com

55. Thank you to our sponsors