Lesson 5 Part 2 - Single Site Replication
Video Activity
Single Site Replication This lesson covers single site replication. Single site replication integrates with VSS and VMWare tools and creates quiescent copies of virtual machines (VMs) and apps. It works above the VMDK level and allows for different types of storage and supports snapshots. The configuration is all done via the web client.
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or
Already have an account? Sign In »
Video Description
Single Site Replication This lesson covers single site replication. Single site replication integrates with VSS and VMWare tools and creates quiescent copies of virtual machines (VMs) and apps. It works above the VMDK level and allows for different types of storage and supports snapshots. The configuration is all done via the web client.
Video Transcription
00:04
Hello and welcome to part two of three for the replication introduction. So one of the scenarios we can think about is a single site replication
00:15
V R integrates with volume, shadow copy service or V s s that also integrates with them or tools. So it takes advantage of some of the features that V, S S and D M where tools offers,
00:28
for instance, we can create a quiescent copy of a virtual machine and an application
00:33
or or APS. And when we say quest and copy, what we mean is that the
00:38
the B. M s slow down and copied so that we can get all the memory, state and data that's in memory. And any disk
00:46
storage changed blocks all accounted for because the VM has slowed down to the point where we could make copies without me and other changes happening in the middle of that process.
00:57
So v. R works at the virtual device later. This is above your V M. D K level.
01:03
This is why we can, uh,
01:07
used different types of storage, and we're also
01:10
the snapshots could be supported.
01:12
So independent of the disc format is really great aspect of this feature.
01:19
So we can, um,
01:21
not support fault Tyler V. EMS Link clones or VM templates with this kind of a scenario. So do be aware those
01:29
three items are not supported.
01:30
You do need virtual hardware version seven or later,
01:37
and the most aggressive recovery point objective you can have is 15 minutes.
01:42
Well, you can stretch that all the way up to 24 hours. So depending on your requirements
01:47
and the amount of data that needs to be replicated and how often you're
01:52
you're vey EMS changed their data,
01:55
then you might have to pick a different recovery are different r p o to best fit your needs.
02:00
So if we look at this single site
02:02
scenario, we've got RV sphere. Client of the center has its own storage. Then we have the V R appliance. Remember, this is an ovf format appliance for V spare replication.
02:14
We have our two V's fear environments with the V R agent running in each of those environments, and then we have a connection to our storage.
02:23
So
02:25
when a replication begins,
02:30
the data coming from
02:32
ah, the sphere,
02:34
the source or the target V sphere
02:37
is this line in green,
02:39
all of the deltas, all the changes in and data blocks
02:44
get copied to V R Appliance,
02:47
which then uses Network file copy or NFC to manage where that data go. So from the source to the target and generals, what we're thinking about here,
02:58
the configuration of replication is all done through the Web client. As I said, it's got full integration with my client,
03:05
and the agents tracked those changes and send those blocks to the V R Appliance so we can keep track of
03:12
changing data blocks and then decides which wants to copy,
03:15
uh to the to the actual stores using network file copy,
03:22
so tracks the changes and moves the date around as needed.
03:27
Another scenario
03:29
would be to have something like remote office,
03:31
where you're doing replication using a feat, a single V center.
03:38
In this case, we have every spare client V our clients again,
03:40
um, to virtual are two V spare replication servers
03:46
with V sphere running on a similar scenarios. We see here
03:52
with three different discs. In this case, B, M D. K. 12 and three.
03:55
We're still copying the change blocks
04:00
in the same fashion as we did before. But the remote office has its own V spear
04:06
configurations with the V's Fear agent running on
04:11
both both of these v spheres.
04:13
Because we can see here
04:15
and this case because of the way that the replication is being done. V. M D K one and three end up with with with this storage area and the MDK two might end up in a different storage area. And then this network file copy goes between your main office and your remote office.
04:33
So, to recap, we went over the architecture for a single site. Replication architectures what we see here
04:40
showing our agents running on the two V's fear environments, knowing again that we can use any disc format that's required.
04:47
Remember that fall tolerantly clones and templates are not supported. You need virtual hardware number our version seven or later,
04:56
and then you're
04:58
recover. The point objective could be 15 minutes all the way to 24 hours.
05:02
Then we look at how you might do this replication with a remote
05:06
office showing how the data flows the lines and green, in this case will move between your home office V sphere, replication set up, and the remote office
Up Next
Similar Content
