Professional Documents
Culture Documents
Module 3.3
Local Replication
After completing this module you will be able to: Discuss local replication and the possible uses of local replicas Explain consistency considerations when replicating file systems and databases
Local Replication - 2
Local Replication - 3
What is Replication
Replica - An exact copy Replication - The process of reproducing data
Local replication - Replicating data within the same array or the same data center
REPLICATION
Source
2009 EMC Corporation. All rights reserved.
Replica (Target)
Local Replication - 4
Decision support
Testing platform Data Migration
Local Replication - 5
Replication Considerations
Types of Replica: choice of replica tie back into RPO
Point-in-Time (PIT)
non zero RPO
Continuous
near zero RPO
Consistency
Ensuring consistency is primary requirement for all the replication technologies
Local Replication - 6
Understanding Consistency
Consistency is required to ensure the usability of replica Consistency can be achieved in various ways:
For file Systems
Offline: Un-mount file system Online: Flush host buffers
For Databases
Offline: Shutdown database
Online: Database in hot backup mode
Dependent Write I/O Principle By Holding I/Os
Local Replication - 7
Source
Replica
Local Replication - 8
Replica
Consistent
Inconsistent
Local Replication - 10
Consistent
Local Replication - 11
Lesson Summary
Key points covered in this lesson: Possible uses of local replicas
Alternate source for backup Fast recovery
Decision support Testing platform Data Migration
Recoverability and Consistency File system and database replication consistency Dependent write I/O principle
2009 EMC Corporation. All rights reserved. Local Replication - 12
Local Replication - 13
Local Replication - 14
Host
Logical Volume
Logical Volume
Physical Volume 1
Physical Volume 2
Local Replication - 15
Requires a fraction of the space used by the original FS Implemented by either FS itself or by LVM
Local Replication - 16
Prod FS Metadata
1 Data a 2 Data b c 3 Data C d 4 Data D
New writes
N Data N
2009 EMC Corporation. All rights reserved.
Snap FS Metadata BLK 1-0 2-0 3-2 4-1 Bit 1-0 2-0 3-1 4-1
N Data N
2009 EMC Corporation. All rights reserved.
Host based replicas can be usually presented back to the same server Keeping track of changes is a challenge after the replica has been created
Local Replication - 19
Replica
Production Server
2009 EMC Corporation. All rights reserved.
BC Server
Local Replication - 20
Good for full backup, decision support, development, testing and restore to last PIT
Attached
Read/Write Not Ready
Source
Array
2009 EMC Corporation. All rights reserved.
Target
Local Replication - 21
Detached - PIT
Read/Write Read/Write
Source
Array
2009 EMC Corporation. All rights reserved.
Target
Local Replication - 22
Attached/ Synchronization
Detached
Resynchronization
Source = Target
Source Target
Source = Target
Local Replication - 23
Local Replication - 24
Source
Target
Write to Target
Read/Write Read/Write
Source
Target
Source
2009 EMC Corporation. All rights reserved.
Target
Local Replication - 25
Local Replication - 26
Typically recommended if the changes to the source are less than 30%
Local Replication - 27
Source
Save Location
Local Replication - 28
Based on the vendor some level of granularity is chosen and a bit map is created (one for source and one for target)
For example one could choose 32 KB as the granularity If any change is made to any bit on one 32KB chunk the whole chunk is flagged as changed in the bit map For 1GB device, map would only take up 32768/8/1024 = 4KB space
Local Replication - 29
At PIT
Target
After PIT
Source Target
1 0
0 0
0 1
1 1
0 0
1 0
0 0
0 1
0 = unchanged
2009 EMC Corporation. All rights reserved.
1 = changed
Local Replication - 30
Restore/Restart Operation
Source has a failure
Logical Corruption Physical failure of source devices Failure of Production server
Solution
Restore data from target to source
The restore would typically be done incrementally Applications can be restarted even before synchronization is complete
Restore/Restart Considerations
Before a Restore
Stop all access to the Source and Target devices Identify target to be used for restore
Based on RPO and Data Consistency
Perform Restore
Pointers to the save location for data was written after PIT
Thus to perform a restore to an alternate volume the source must be healthy to access data that has not yet been copied over to the target
Local Replication - 33
Size of target
Not required
Required
Only after synchronization and Accessibility to target Immediately accessible detachment from the source
Immediately accessible
Local Replication - 34
Source
12:00 P.M.
Point-In-Time
06:00 P.M.
12:00 A.M.
: 12 : 01 : 02 : 03 : 04 : 05 : 06 : 07 : 08 : 09 : 10 : 11 : 12 : 01 : 02 : 03 : 04 : 05 : 06 : 07 : 08 : 09 : 10 : 11 : A.M.
2009 EMC Corporation. All rights reserved.
P.M.
Local Replication - 35
Local Replication - 36
Lesson Summary
Key points covered in this lesson: Replication technologies
Host based
LVM based mirroring File system snapshot
Array based
Full volume mirroring
Pointer-based full volume copy Pointer-based virtual replica
Local Replication - 37
Module Summary
Key points covered in this module: Definition and possible use of local replicas
Local Replication - 38
EMC TimeFinder/Mirror
Full volume mirroring
EMC TimeFinder/SNAP
Pointer based replication
Local Replication - 39