Lesson 5 Part 3 - Main data center replication to remote offices
Video Activity
Main data center replication to remote offices This lesson discusses main datacenter replication to remote offices. This allows you to distribute data geographically to make recovery more efficient in the event of a disaster or fail over. Participants also learn how to recover a VM as well as vSphere replication and site recovery manager (SMS).
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
Main data center replication to remote offices This lesson discusses main datacenter replication to remote offices. This allows you to distribute data geographically to make recovery more efficient in the event of a disaster or fail over. Participants also learn how to recover a VM as well as vSphere replication and site recovery manager (SMS).
Video Transcription
00:04
Hello and welcome to part three of our replication introduction. So now we're looking at a couple are different. One more scenario here. We've got our main data center
00:14
replicating to remove office.
00:16
So much like before, we have our V Star client
00:19
V Center itself with its own storage, our visa replication appliance. Communicating
00:27
then are two V sphere environments here
00:30
with the, uh, V R a, the V's Fear replication Agent running on bull systems.
00:35
I've got my three disks
00:37
and then that network
00:39
file copy in the green lines here showing how that would replicate to a remote office or two are a couple of remote offices.
00:47
I'm gonna be our service in the remote office.
00:50
The sphere environments again using network file copy to move that data. So I've got V M d. K one being replicated to remote office one, let's say,
01:00
or maybe your East Coast office and then v. M. D. K two and three being replicated to your West Coast office
01:07
so it lets you distribute your data geographically If you wish so that you've got enhanced abilities for different kinds of disaster recovery and fail over,
01:19
they're only four basic steps to doing a full recovery of a V M.
01:25
You simply right. Click the BM and select Recover. That's the first step.
01:29
Then you pick the target folder.
01:30
Where were the recovery will happen or it will take world. The files will be stored
01:37
and you pick the target resource. Whether it's a cluster, a host or a resource pool
01:42
and simply click finish on, the process begins
01:45
again. Rep. Uh, this is all done through the Web client.
01:49
And if we think about Feaster replication and site recovery manager,
01:53
we've got a couple different things to talk about. Here.
01:57
Site recovery manager or S R M. These users can use ah, duplication that's built in with with their arrays. So summer raise support duplication other rays. That's a future that depends on which way. You by, of course,
02:12
but you can do a ready duplication and used V R. So you have the ability to use both of those together.
02:19
If V R is already installed, then S R M will will detect that fact and be able to use V R.
02:25
Otherwise you can stop the are during the S R. M install.
02:30
So if you're installing site recover manager, get the option to install these fair replication Pretty handy. Makes your life a little bit easier.
02:38
So building a foundation for disaster recovery can be done with side recovery manager
02:44
and we are together.
02:46
So remember, v r offers protection
02:49
by moving your data around to other replicated sites.
02:53
But s R I'm actually offers
02:57
disaster recovery functionality.
03:00
So in the case of S r. M, you could fail over to one of your remote sites and then be able to adapt your organization to that fact
03:08
fail back, fail over.
03:10
Aah! These v R s A. M do have a couple things in common. They both uses the replication engine and allow you to qui es your APs
03:20
again. Questing the apse means that you're slowing down the processing to the point where all the data can be copied accurately and completely.
03:27
We are, however, uses the next generation Web climb, which is the one you'll see with version five over 51
03:35
and then as an old review some of the functions for psych recovery manager. We can do full disaster recovery orchestration, meaning that once you set up your primary site and your remote site,
03:45
you can dictate how the re
03:47
the disaster recovery synchronization will happen and how the how the recovery will happen. When you move the data back,
03:53
you could do your testing and a non intrusive way.
03:58
So if I have my primary site up and running, I can fail over to the, um,
04:03
not fail over but replicate to the other side
04:08
and not affect the primary site.
04:11
So that lets you test to make sure that your servers and your infrastructure can deal with a actual replication.
04:17
Ah, fail over event
04:19
by testing it and not really affecting your primary site. So it's a nice nice feature to have there.
04:26
We can also do ah, peril of recovery of the EMS or groups of the EMS.
04:31
So depending on how you want a group that you're protected vee EMS, you can set those up and run those multiple replications at the same time in parallel again. That's limited by your network band with and the performance of your hardware somewhat
04:46
once L V M is failed over, we can re protected on the remote site or fail it back, so you have some flexibility in both directions. There
04:56
We can also set up a recovery plan
05:00
so that you could do this on a schedule if you wish, or you can do it manually. Saying I wantto fail over. I want to recover by manually selecting that option.
05:11
I also have the option to do a partial sight recovery or partial sight fail over. You don't have to do everything all at once. You contest small portions or test the entire thing or actually fail over the entire thing or fail over a small portion.
05:25
So again, we have a lot of flexibility here for how v, r and S r M can work together.
05:30
And then because we have all the automation possibilities for developers, they can use the AP eyes if they wanted to write their own applications, that can interface with S R. M.
05:42
And we have a lot of different reporting functions that will tell you things like, how long did it take to replicate my data between this B. M the source B m in the target GM, how long did it take
05:53
to replicate the data with between all my viens on the source environment to the remote site?
05:59
How long did it take to fail over to fail back. You can see all those different aspects way and the reporting function.
06:04
So to recap,
06:06
we looked at how you might set up replication going to multiple officers.
06:13
We know that's four simple steps to do the full recovery of a V. M.
06:17
We talked about some of the integration between V R and S are Emma's faras,
06:23
as are on being able to take advantage of the RV. It's installed.
06:28
And then we look at some of the different features that via offers we worked with the Web client.
06:34
They both share the replication engine and the ability to create asked your applications.
06:39
And then we went over some of the S R. M functions, like basically telling you how you can integrate the two products together to do full
06:47
disaster recovery planning in a nondestructive way.
Up Next
Similar Content
