sharepoint native backup/restore capabilities configuration settings service applications unattached...
TRANSCRIPT
SharePoint 2013 Backup and Recovery with DPM 2012Chris Whitehead & Sam HassaniPremier Field Engineering
SPC208
Who are we?Chris Whitehead
• Premier Field Engineer
• Microsoft Certified Master (MCM) SharePoint 2010
• PFE EMEA SharePoint Tech Lead
Sam Hassani
• Premier Field Engineer
• Microsoft Certified Master (MCM) SharePoint 2010
• SharePoint Beta Support
[email protected]@mrwhitey
[email protected]@samhassa
Blog: http://sharepoint.microsoft.com/blogs/fromthefield
SharePoint native backup/restore recap
SharePoint native backup/restore capabilities
• Configuration settings• Service Applications• Unattached content database recovery• SQL Snapshot support
SharePoint native backup/restore limitations
• In-line item level recovery• Configuration and Central Admin database restore
What does DPM give us?
DPM capabilities
• In-line item level recovery• Configuration and Central Admin database restore• Less storage required for backups• Backup to the cloud• Role based backup and recovery management and administration• Protection of other Microsoft products e.g. Hyper-V
DPM limitations
• Service Applications
DPM 2012
Online Snapshots
Disk-Based Recovery
Active Directory
Tape-Based Backup
Data Protection Manager
Up to Every 15 minutes
Disaster Recoverywith offsite replication and tape
Data Protection Manager
DPM scalability
100 DPM servers or 50,000 data sources centrally managed
Then, per DPM server…
2000 SQL Server databases
100 production servers and 3000 Windows client machines
80TB Exchange data
25TB SharePoint data
Protecting SharePoint data
Configuration
Create and configure a protection group
Configure the WSS Writer service with ConfigureSharePoint.exe
Install the DPM agent
ConfigureSharePoint.exe
One tick ‘farm’ protectionSQL Server 1
E:\ +ContentDB1.mdf +ContentDB1.ldf
F:\
+ContentDB2.mdf +ContentDB2.ldf
G:\ +ConfigDB.mdf +ConfigDB.ldf
SQL Server 2
D:\ +ContentDB3.mdf +ContentDB3.ldf
E:\ +ContentDB4.mdf +ContentDB4.ldf
Backup: data flow
SharePoint server Database servers
DPM server
VSS Writers
Backup: data flow
SharePoint server Database servers
DPM server
VSS Writers
Demo: Protecting SharePoint dataChris Whitehead, Sam Hassani
Under the hood…
Before backup
DPM Filter – Volume Map
SQL Server 1
E:\ +ContentDB1.mdf +ContentDB1.ldf
F:\
+ContentDB2.mdf +ContentDB2.ldf
G:\ +ConfigDB.mdf +ConfigDB.ldf
SQL Server 1
E:\ +ContentDB1.mdf +ContentDB1.ldf
F:\
+ContentDB2.mdf +ContentDB2.ldf
G:\ +ConfigDB.mdf +ConfigDB.ldf
Start of synchronization window
Volume (actual disk blocks)
Time = 10:00
DPM Filter – Volume Map
1st change
1 2 3 4
Volume (actual disk blocks)
Time = 10:01
DPM Filter – Volume Map
File Write Changed Blocks Noted
2nd change
7
1 2 3 4
5
6
8 9
Volume (actual disk blocks)
Time = 10:06
DPM Filter – Volume Map
File Write Changed Blocks Noted
3rd change
11 7
1 2 3 4
12
5
6
15
8 9
10 13 14
Volume (actual disk blocks)
Time = 10:18
DPM Filter – Volume Map
File Write Changed Blocks Noted
Synchronization starts (express full backup)
11 7
1 2 3 4
12
5
6
15
8 9
10 13 14
Volume (actual disk blocks)
Time = 10:30
DPM Filter – Volume Map
Synchronization VSS Snapshot Taken
11 7
1 2 3 4
12
5
6
15
8 9
10 13 14
Synchronization starts (express full backup)
11 7
1 2 3 4
12
5
6
15
8 9
10 13 14
Volume (actual disk blocks)
Time = 10:30:01
DPM Filter – Volume Map
Synchronization Changed Blocks Sent to DPM
4th change
11 7
1 2 3 4
19 12
5 16 17 18
6
15
8 9
10 13 20 14
Volume (actual disk blocks)
Time = 10:30:02
DPM Filter – Volume Map
Synchronization File I/O ContinuesFile Write
Synchronization ends
11 7
1 2 3 4
19 12
5 16 17 18
6
15
8 9
10 13 20 14
Volume (actual disk blocks)
Time = 10:30:03
DPM Filter – Volume Map
VSS Snapshot ReleasedVolume Map ResetFile Write
19
16 17 18
20
Efficient disk storage without duplication
A B C D E F G
Production Data
H A B C D E F G
DPM Replica
H
Original Data (10:00)
Time = 10:00
Efficient disk storage without duplicationTime = 10:15 – Data changes
A B I D E J G
Production Data
H A B C D E F G
DPM Replica
H
Original Data (10:00)
Efficient disk storage without duplicationTime = 10:30 – Data is protected
A B I D E J G
Production Data
H A B C D E F G
DPM Replica
HI J
Original Data (10:00)1st Express Full Backup (10:30)
Efficient disk storage without duplicationTime = 10:30 – Data is protected
A B I D E J G
Production Data
H A B
C
D E
F
G
DPM Replica
HI J
Original Data (10:00)1st Express Full Backup (10:30)
Efficient disk storage without duplicationTime = 10:30 – Data is protected
Production Data DPM Replica
DPM Recovery Point AreaC F
A B I D E J G H A B D E G HI J
Original Data (10:00)1st Express Full Backup (10:30)
Efficient disk storage without duplicationTime = 10:52 – Data changes
Production Data DPM Replica
C F
K B I D E J L H A B D E G HI J
Original Data (10:00)1st Express Full Backup (10:30)
DPM Recovery Point Area
Efficient disk storage without duplicationTime = 11:00 – Data is protected
Production Data DPM Replica
C F
K B I D E J L H A B D E G HI JK L
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)
DPM Recovery Point Area
Efficient disk storage without duplicationTime = 11:00 – Data is protected
Production Data DPM Replica
C F
K B I D E J L H
A
B D E
G
HI JK L
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)
DPM Recovery Point Area
Efficient disk storage without duplicationTime = 11:00 – Data is protected
Production Data DPM Replica
K B I D E J L H B D E HI JK L
AC F G
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)
DPM Recovery Point Area
Efficient disk storage without duplicationTime = 11:07 – Data changes
Production Data DPM Replica
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)
B D E HI JK L
AC F G
K B I D M N O P Q
DPM Recovery Point Area
Efficient disk storage without duplicationTime = 11:30 – Data is protected
Production Data DPM Replica
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)3rd Express Full Backup (11:30)
B D E HI JK L
AC F G
K B I D M N O P Q M N O P Q
DPM Recovery Point Area
Efficient disk storage without duplicationTime = 11:30 – Data is protected
Production Data DPM Replica
AC F G
K B I D M N O P Q B D
E H
I
J
K
L
M N O P Q
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)3rd Express Full Backup (11:30)
DPM Recovery Point Area
Efficient disk storage without duplicationTime = 11:30 – Data is protected
Production Data DPM Replica
K B I D M N O P Q B DIK M N O P Q
AC EF G HJ L
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)3rd Express Full Backup (11:30)
DPM Recovery Point Area
Efficient disk storage without duplicationTo recover to: 11:00
Production Data
A
B
C
D
EF G
DPM Replica
H
I
J
K
L
M N O P QK B I D E J L H 8 Blocks Restored
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)3rd Express Full Backup (11:30)
DPM Recovery Point Area
Efficient disk storage without duplicationTo recover to: 10:00
Original Data (10:00)1st Express Full Backup (10:30)2nd Express Full Backup (11:00)3rd Express Full Backup (11:30)
Production Data
A
B
C
D
EF G
DPM Replica
H
I
J
K
L
M N O P QA B C D E F G H 8 Blocks Restored
DPM Recovery Point Area
Recovering SharePoint data
Recovery: data flow (databases)
SharePoint server Database servers
DPM server
Recovery: data flow (sites, lists, and items)
SharePoint server Database servers
DPM server
CMP
Recovery: data flow (sites, lists, and items)
SharePoint server Database servers
DPM server
CMP
1010010 101 1101011 00010101 010010 10100 1010111 100 1010 01001
Recovery: data flow (sites, lists, and items)
SharePoint server Database servers
DPM server
Recovery farm
CMP
Demo: Recovering SharePoint dataChris Whitehead, Sam Hassani
Recovering SharePoint dataRecovery farm needed in some cases
• Recovery farm web application must be named “DPMRecoveryWebApplication”
Full farm restore requires same farm configuration
Caveats of SharePoint export/import
DPM vs. SQL Server backup
SQL Server backups250 GB of SQL Server databases
30 GB
15 GB
12 GB
18 GB
Assume 70% compression during backup
75 GB per backupFor 2 weeks:75 GB x 14d = ~1 TB
100 GB 50 GB 40 GB 60 GB
DPM backups
250 GB DPM replica
For 2 weeks:250 GB + 375 GB = 625 GB
100 GB 50 GB 40 GB 60 GB
375 GB DPM recovery point area
250 GB of SQL Server databases
10 GB
5 GB 4 GB 6 GBAssume 10% data change rate per day
25 GB per day x 13 days
DPM backups
250 GB DPM replica
For 2 weeks:250 GB + 168 GB = 418 GB
100 GB 50 GB 40 GB 60 GB
168 GB DPM recovery point area
250 GB of SQL Server databases
5 GB 2.5 GB
2 GB 3 GBAssume 5% data change rate per day
12.5 GB per day x 13 days
Summary
DPM compliments the out of the box backup and recovery tools, providing simple, fast, and automated backup and recovery.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Evaluate this session now on MySPC using your laptop or mobile device: http://myspc.sharepointconference.com
MySPC