• • • • • • http://sharepoint.microsoft.com/blogs/fromthefield 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.

Download Report

Transcript • • • • • • http://sharepoint.microsoft.com/blogs/fromthefield 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.

•
•
•
•
•
•
http://sharepoint.microsoft.com/blogs/fromthefield
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
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
Online Snapshots
Disk-Based
Recovery
Active Directory
Up to
Every 15 minutes
Data Protection Manager
Data Protection Manager
Disaster Recovery
with offsite replication and tape
Tape-Based
Backup
Install the DPM agent
Configure the WSS Writer service with ConfigureSharePoint.exe
Create and configure a protection group
SharePoint server
VSS Writers
DPM server
Database servers
SharePoint server
VSS Writers
DPM server
Database servers
DPM Filter – Volume Map
Time = 10:00
Volume (actual disk blocks)
DPM Filter – Volume Map
Time = 10:01
1
Volume (actual disk blocks)
File Write
2
3
Changed Blocks Noted
4
DPM Filter – Volume Map
Time = 10:06
File Write
Changed Blocks Noted
7
1
2
3
4
5
6
8
Volume (actual disk blocks)
9
DPM Filter – Volume Map
Time = 10:18
File Write
11
Changed Blocks Noted
7
1
2
3
4
12
5
6
15
8
10
Volume (actual disk blocks)
9
13
14
DPM Filter – Volume Map
Time = 10:30
Synchronization
11
VSS Snapshot Taken
7
1
2
3
4
12
5
6
15
8
10
Volume (actual disk blocks)
9
13
14
DPM Filter – Volume Map
Time = 10:30:01
11
Synchronization
Changed Blocks Sent to DPM
7
1
2
3
4
12
5
6
15
8
10
Volume (actual disk blocks)
9
13
14
DPM Filter – Volume Map
Time = 10:30:02
11
Synchronization
File Write
File I/O Continues
7
1
19
2
3
17
18
4
12
5
16
6
15
8
10
Volume (actual disk blocks)
9
13
20
14
DPM Filter – Volume Map
Time = 10:30:03
11
File Write
VSS Snapshot Released
Volume Map Reset
7
1
19
2
3
17
18
4
12
5
16
6
15
8
10
Volume (actual disk blocks)
9
13
20
14
DPM Filter – Volume Map
Time = 10:00
Production Data
DPM Replica
A B C D E F GH
A B C D E F GH
Original Data (10:00)
Time = 10:15 – Data changes
Production Data
DPM Replica
A B I D E J GH
A B C D E F GH
Original Data (10:00)
Time = 10:30 – Data is protected
Production Data
A B I D E J GH
Original Data (10:00)
1st Express Full Backup (10:30)
DPM Replica
I J
A B C D E F GH
Time = 10:30 – Data is protected
Production Data
DPM Replica
A B I D E J GH
A B I D E J GH
C
Original Data (10:00)
1st Express Full Backup (10:30)
F
Time = 10:30 – Data is protected
Production Data
DPM Replica
A B I D E J GH
A B I D E J GH
Original Data (10:00)
1st Express Full Backup (10:30)
DPM Recovery Point Area
C F
Time = 10:52 – Data changes
Production Data
DPM Replica
K B I D E J L H
A B I D E J GH
Original Data (10:00)
1st Express Full Backup (10:30)
DPM Recovery Point Area
C F
Time = 11:00 – Data is protected
Production Data
K B I D E J L H
Original Data (10:00)
1st Express Full Backup (10:30)
2nd Express Full Backup (11:00)
DPM Replica
K L
A B I D E J GH
DPM Recovery Point Area
C F
Time = 11:00 – Data is protected
Production Data
DPM Replica
K B I D E J L H
K B I D E J L H
A
Original Data (10:00)
1st Express Full Backup (10:30)
2nd Express Full Backup (11:00)
G
DPM Recovery Point Area
C F
Time = 11:00 – Data is protected
Production Data
DPM Replica
K B I D E J L H
K B I D E J L H
Original Data (10:00)
1st Express Full Backup (10:30)
2nd Express Full Backup (11:00)
DPM Recovery Point Area
C F AG
Time = 11:07 – Data changes
Production Data
DPM Replica
K B I DMNO P Q
K B I D E J L H
Original Data (10:00)
1st Express Full Backup (10:30)
2nd Express Full Backup (11:00)
DPM Recovery Point Area
C F AG
Time = 11:30 – Data is protected
Production Data
K B I DMNO P Q
DPM Replica
MNO P Q
Original Data (10:00)
1st Express Full Backup (10:30)
2nd Express Full Backup (11:00)
3rd Express Full Backup (11:30)
K B I D E J L H
DPM Recovery Point Area
C F AG
Time = 11:30 – Data is protected
Production Data
DPM Replica
K B I DMNO P Q
K B I DMNO P Q
E J L H
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
C F AG
Time = 11:30 – Data is protected
Production Data
DPM Replica
K B I DMNO P Q
K B I DMNO 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
C F AG E J L H
To recover to: 11:00
Production Data
K B I D E J L H
DPM Replica
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)
K B I DMNO P Q
DPM Recovery Point Area
C F AG E J L H
To recover to: 10:00
Production Data
A B C D E F GH
DPM Replica
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)
K B I DMNO P Q
DPM Recovery Point Area
C F AG E J L H
SharePoint server
DPM server
Database servers
SharePoint server
DPM server
Database servers
SharePoint server
DPM server
Database servers
SharePoint server
DPM server
Database servers
Recovery 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
250 GB of SQL Server databases
Assume 70%
compression
during backup
100 GB
50 GB
40 GB
60 GB
30 GB
15 GB
12 GB
18 GB
For 2 weeks:
75 GB x 14d = ~1 TB
250 GB of SQL Server databases
100 GB
Assume 10%
data change
rate per day
10 GB
50 GB
5 GB
40 GB
4 GB
60 GB
6 GB
25 GB per day
x 13 days
For 2 weeks:
250 GB + 375 GB = 625 GB
250 GB of SQL Server databases
100 GB
Assume 5%
data change
rate per day
5 GB
50 GB
2.5 GB
40 GB
2 GB
60 GB
3 GB
12.5 GB per
day x 13 days
For 2 weeks:
250 GB + 168 GB = 418 GB
automated
simple fast
MySPC
http://myspc.sharepointconference.com