SIM213 Online Snapshots (up to 512) Disk-based Recovery Active Directory® System State Up to Every 15 minutes Data Protection Manager Data Protection Manager Disaster Recovery with offsite replication & tape Tape-based Backup file.

Download Report

Transcript SIM213 Online Snapshots (up to 512) Disk-based Recovery Active Directory® System State Up to Every 15 minutes Data Protection Manager Data Protection Manager Disaster Recovery with offsite replication & tape Tape-based Backup file. 

SIM213
Online Snapshots (up to 512)
Disk-based
Recovery
Active Directory®
System State
Up to
Every 15 minutes
Data Protection Manager
Data Protection Manager
Disaster Recovery
with offsite replication & tape
Tape-based
Backup
file services
Back end server 1
E:\
+ ContentDB1.mdf
+ ContentDB1.ldf
F:\
+ ContentDB2.mdf
+ ContentDB2.ldf
G:\
+ ConfigDB.mdf
+ ConfigDB.ldf
Back end server 2
D:\
+ ContentDB3.mdf
+ ContentDB3.ldf
E:\
+ ContentDB4.mdf
+ ContentDB4.ldf
DPM filter creates a volume map to monitor which disk blocks
contain portions of the files to be protected
E:\
+ ContentDB1.mdf
+ ContentDB1.ldf
F:\
+ ContentDB2.mdf
+ ContentDB2.ldf
DPM Filter – Volume Map
Time = 10:00
10:01
10:30
10:06
10:18
10:26
(At least weekly… usually daily … up to every 30 minutes)
File Write
VOLUME (actual disk blocks)
11
7
1
16
17
2
18
3
19
4
12
5
6
DPM Filter – Volume Map
Changed
blocks noted
1.
VSS Snapshot
taken on production
volume to ensure consistent data
15
8
10
9
13
14
Time = 10:30:01
DPM Synchronization
VOLUME (actual disk blocks)
11
7
1
16
17
18
19
4
12
5
6
DPM Filter – Volume Map
1. VSS Snapshot taken on production
volume to ensure consistent data
2. Cache of changed blocks is sent to DPM
server
15
8
9
10
Block Order
13
14
13
10
9
8
15
14
6
5
12
4
19
18
17
16
1
7
11
Transmit changed blocks from 10:00-10:30 to DPM server Data integrity preserved, since volume snapped
Time = 10:30:03
02
DPM
And File
Synchronization
IO continues
VOLUME (actual disk blocks)
1
2
3
4
5
6
18
19
20
7
8
9
10
11
DPM Filter – Volume Map
21
12
13
22
15
Block Order
14
16
17
16
15
14
13
12
1. VSS Snapshot taken on production
volume to ensure consistent data
2. Cache of changed blocks is sent to DPM
server while live disk continues.
server,
17
11
10
9
8
7
6
5
4
3
2
1
Time = 10:30:04
And File IO continues
VOLUME (actual disk blocks)
1
2
3
4
5
6
18
19
20
7
8
9
10
11
DPM Filter – Volume Map
21
12
13
15
22
16
14
17
1. VSS Snapshot taken on production
volume to ensure consistent data
2. Cache of changed blocks is sent to DPM
server, while live disk continues.
3. Frozen blocks from snapshot are
released
Production Server
DPM Replica
Database
Database
0:00
Baseline Initial Mirror
0:00
Production Server
DPM Replica
Database
Database
0:XX
15 minute Syncs
Every 15 minutes, closed transaction logs are
sent to the DPM server
0:00
Production Server
DPM Replica
Database
0:XX
Database
Restore
DPM can restore server to any 15 minute point in
time
0:00
Production Server
DPM Replica
Database
Database
1:XX
1:00
Day
At least
1 : Data
weekly
changes
but usually daily,
a DPM Express Full re-synchronizes
the DPM Replica
15 Minutes
Express
Full
1:00
0:00
Shadow Copy
of 0:00 to 1:00
+
Transaction logs
Day 0
0:00
Production Server
DPM Replica
Database
1:XX
DPM can restore to
Yesterday
at 10:45
Today
at 2:15
Use
existing
Shadow
copy1:00
0:00replica
to rebuild day 0
Roll forward logs to 2:15
yesterday at 10:45
Database
15 Restore
Minutes
1:00
Shadow Copy
of 0:00 to 1:00
+
Transaction logs
Day 0
0:00
Production Server
DPM Replica
Database
2:00
Database
1:00
2:00
Express Full
Up to 512
Week
2 : shadow copies, plus their logs
Express Full - resynchronization
512w x 7d x 24h x 4(15m) = 344,000 Recovery
Points
Shadow Copy
of 0:00 to 1:00
+
Transaction logs
Day 0
0:00
1:00
Replica dB1
Replica Volume
Shadow Copy dB1
Shadow Copy Volume
db1
db2
dbN
file services
Basic DPM idea
Each production “datasource” = 2 Volumes on the DPM server
e.g. SQL Database … Virtual Machine … File Volume
Replica DS1
Shadow Copy DS1
Replica DS2
Shadow Copy DS2
Replica DSn
Shadow Copy DSn
db1
db2
Replica Volume
Shadow Copy Volume
dbN
Windows Disk Administrator
file services
300 DB’s = 600 Partitions. Stretched = 800, 900, 1000 <stop>
DPM 2007
Shadow Copy DS1
Replica DS1
Replica DS2
Shadow Copy DS2
Replica DSn
Shadow Copy DSn
db1
db2
Shadow Copy Volume
Replica Volume
dbN
DPM 2010
file services
Replica DS1
Replica DS2
Shadow Copy
DS1 DS2 … DSn
Replica DSn
Replica Volume
Shadow Copy Volume
DPM Agent
VSS Requester
VSS
VSS Provider
VSS Writer
Virtual Machine
Hyper-V IC
VSS
Shadow Copy
03:02:21
VSS
Shadow Copy
03:02:45
?
Virtual Machine
Shadow Copy
Hyper-V IC
Clean-Up
VSS
Shadow Copy
03:02:21
VSS
Shadow Copy
Volume
VHD
Shadow Copy
03:02:45
?
FS1 \ data
(share)
AccountingdB
(SQLdb)
Mailboxes
(Exch)
FS2 E:\team
(directory)
DPM
FS1_data (share)
SQL8\AccountingdB (sql)
EX10\SG1\Mailboxes (exchange)
FS2_E:\team\ (directory)
DPM DR
FS1_data (share)
SQL8\AccountingdB (sql)
EX10\SG1\Mailboxes (exchange)
FS2_E:\team\ (directory)
October 2010
Blue Section
http://www.microsoft.com/cloud/
http://www.microsoft.com/privatecloud/
http://www.microsoft.com/windowsserver/
http://www.microsoft.com/windowsazure/
http://www.microsoft.com/systemcenter/
http://www.microsoft.com/forefront/
http://northamerica.msteched.com
www.microsoft.com/teched
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn