Hello, I'm Gene Campiglio
and welcome to Cyber Eri were
in module 11. Lesson number five. Now for the virtual ization
Well, now we're gonna be talking about replication.
So we'll we'll describe what replication actually is.
Some of the configuration parameters that you might encounter
and how the VM recovery is done.
And then we'll talk about how replication works in a disaster recovery context.
This lesson will be in two parts,
starting off with wood replication actually is. This is replication at the hyper visor level.
works also at the host level.
But because we're replicating V's fear to these fear, I might source be sphere with my various be EMS
in my target, the sphere with my various PM's.
If you're using the Web client, there's full integration with with a VCR, replication or V R with your Web client.
And one of the really nice features is that any storage type can be used, including local storage
I could also replicate to any storage at the fail oversight, including local stores, so you can have a V M F s I scuzzy local storage NFs
it lets you use any of those in mix and match, which is, Ah, wonderful bit of flexibility to offer to the administrator, especially when
when your primary site is where you invested most of your money and equipment. Maybe your fail oversight has less powerful systems and more inexpensive storage, so you can still use replication in that kind of scenario. So it's really nice for saving a little bit of money.
So when this works, is that
When replication begins, it creates a shadow bm at the destination site.
Once the shadow VM gets created, then replication of the data starts to begin
is applied or rather deployed as an ovf appliance,
and it comes with most standard additions.
I'm sorry come with most V sphere additions.
Speaking of the supported versions we can see here
of the center, five got one with Web Client is supported, the beast replication supported.
It's not supportive for V Center 50 older. So be aware of that.
The store 51 and the spare 50 also supported,
but not for four X and older four dot exe.
We can also do storage of emotion and asked an SDRs are storage distributed resource scheduler that supported
We can do, ah, stand alone
side recovery manager or S R M. That's supported.
However, US S R M Version five
does not work with V spear replication, so that is not supported. Be aware of that. Gotcha there.
And then, as far as a different database choices, we have the embedded database, which is what we've built for the lab that you will be watching.
And you also have options for D B to Oracle or sequel server. All those air also supported.
So as far as how replication actually works
first, we have to think about deploying the ovf appliance
so that that builds your your components in your environment for doing V scare replication.
Then you pair your source PM with the destination via.
And lastly, once you configure the virtual machine for Easter replication, then replica than the memory replication can begin
and several things get creative. First we get the recovery point object or our p O.
This means that your
depending on your configuration, the side of the V m. The speed of your network.
on a time basis what your recovery point will be Once you set the V M up for replication,
we also get a target folder created for the VM. If that exists on the source ah, Target day store,
we specify the host.
If it's a cluster, will specify that.
And if your resource pools are in use, then those will also be specified.
So the way this works is that we only replicate changed blocks of data.
This allows for much greater efficiency for dealing with the replication process.
So first, the V R agent will make sure that both disks on both sites so our source site or the target site making sure those are consistent,
meaning that the data is the same
Then the V R agent will track on Lee those blocks that change by using what's called the V's cosy filter.
So if data changes on the source
of'em than that Merck that block it's marked as a block that's changed. And now that
changed block will be replicated
according to your recovery point objective. The R P. O.
And the last thing to talk about here is that it's using TCP ports for 4046 so be aware of that.
So it's a recap we talked about at a high level.
How Visa replication worked at the hyper Visor host level software based.
We know that it works with the Web client.
We talked about its flexibility for using different types of storage on the source
and target environments very, very useful for the budget minded administrator.
And we had an overview of which versions of the Center V sphere
and some of the distributed service's is compatible with V R.
And last we recovered a little bit how v r works, what kinds of objects get created when you configure of'em for
for, ah replication.
And then we discussed how on Lee there changed blocks, get moved over the network to the other site.