Hello and thanks for coming back to Cyber Aires. Microsoft Azure Administrator. A Z 103 Course. This is Episode 33 about azure site recovery and my name's Will Carlson. In today's episode, we're going to go through and talk about just that. What is at your side recovery and particularly how it helps us as administrators
automate and do a lot of the heavy lifting
for D. R or disaster recovery, planning and work flows
to get started here with azure side recovery, I'm gonna go ahead and search for recovery. Service is vault here, and we set up a recovery service is bold. In a previous episode, I'm gonna go ahead and select into that particular recovery. Service is bold
and click on Replicate.
Now with Recovery Service is vault or sorry with as your sight recovery. We have a couple of options here, and interestingly, as your sight recovery can be used to back up on premise workloads as well. And it supports Bert VM wear hyper V and also physical limits and Windows machines.
And really, the magic here of azure site recovery is that it automates and handles a lot of the fail over replication and recovery tasks that we would have had to set up previously. But to show that I'm gonna leave this selected as Azure for now
and now we select the location or the region where our resource is that we want to use A s are for our at. I'm gonna go ahead and select central us, and you can see that Azure is complaining at us. And it's doing this because it wants to make sure we have adequate separation between all of the parts of azure site recovery. And those are
the recovery service is bald,
the resource group that contains those things and the virtual machines themselves. If two of those things are in the same region than we've lost the resiliency that site recovery provides.
For example, if our virtual machines and our recovery service is vault are in the same region and that region goes down then as your sight recovery simply won't work with just a resource group container,
we're gonna go back out here to the recovery service is vaults that we have set up
and I'm gonna select this other side recovery. Recovery service is vault that I set up in a completely different region than the rest of my resource is.
We're gonna go back to replicate,
and you can see now that I'm able to actually step through this without azure complaining,
I'm gonna go ahead and select this particular resource group
And now I can see the virtual machines that are available in that region in that resource group for as your sight recovery I can select. Okay, Here
and now, I have some settings to configure. Now, keep in mind that as your sight recovery is limited based on region, So you've got to make sure all of the regions are gonna be supported for what you're wanting to do, and it is limited to a certain subset of operating systems. So
do a little bit of leg work up front when you're deploying virtual machine images and make sure that the operating systems that you're deploying are covered.
As a real honest example, I had gone through this video recording it with a gun to 18 virtual machines set up only to remind myself that that's not a supported operating system for azure site recovery. So here we are, with the windows 2016 operating system and I'm good to go.
And here are a number of things that I can configure and tweak to my needs. And the 1st 1 is going to be the target location. And this is the location of the replicated virtual machines. Clearly, it would make a lot of sense. Toe, have this be close enough to your physical location. That network is in Leighton. See are good.
But you do have a selection here of where you want those to go,
which is nice. We're gonna go ahead and leave this North Central. That's relatively close.
We can also customize what subscription these replicated machines they're going to run in.
There are a number of networking changes that we can make. We've already got, ah,
virtual network set up for this. So we're gonna leave that as default
and then down here under replication policy, we can set both the recovery point and a nap. Consistent snapshot frequencies as it set right now, we're gonna be taking a snapshot of the environment every 24 hours and we're gonna be taking an app consistent snapshot every four hours. You can change this to be whatever you'd like
and multi bm Consistency just creates a replication group so that multiple v EMS can be maintained consistent together and essentially groups them altogether within one replication policy. That's not necessary here for our one B m. So I'm gonna go ahead and select okay with the defaults.
And now we can go ahead and create those Target Resource is now This is another deployment that's going to take a relatively significant amount of time because what Azure is doing is replicating our workload over the wire to the other region that we selected another. All these resources are created. I can go ahead and click to enable replication.
And then if we click here into replicated items,
we'll ultimately see when the replication has completed. Now, while that site recovery is deploying, I can scroll down here in this blade and look for sight recovery jobs to see what it's up to.
And you get an idea of all the steps that are necessary to create this site recovery. That Azure has completely automated for me, and all I had to do was stepped through a relatively simple wizard based config.
Now that the site recovery job is well enough along the way in the process, I can come up here to replicated items
and see my sight replication here. If I click on into this, I get some more detail about the side replication, and I can see that's enabling protection.
You'll notice here at the top that you can go ahead and do a full fail over. You could test the fail over,
and then once you've tested the fail over, you can even clean up the fail over.
There are also a host of other options here. Then they all become available to you. Once the initial setup of this, as your sight recovery and replication has completed
down here towards the bottom, you can even see where our source location is. And our destination site recovery location is as well
again from start to finish. The azure site recovery setup process does take a little bit of time, but thankfully, due to the way azure is set up, it is largely automated. All we have to do is administrators is click a few buttons and then wait.
I highly recommend you step to the process of setting up your own A s are set up
in your azure environment, let it complete all the way through and then walk through the process of testing and failing over the entire process to see what that's gonna look like. Functionally.
In this episode, we talked very specifically about azure site recovery and how it can help us manage our disaster recovery plans.
And although there are a number of steps and pre considerations about what regions resource is air located in to make sure site recovery ultimately works, essentially, it's a set of wizard based setups that we click through. We tap a couple of buttons, and we have full
site recovery and disaster recovery built into the azure environment. For both as your workloads
and for on premise workloads. Edgar Side Recovery is a really powerful suite of tools here in the azure environment. I hope you'll dive in and see how it figures in both to your current environment and also how you can understand those concepts very well for a Z 103
coming up. Next, we're gonna go back a little more simple than full on site recovery, and we're gonna talk about how we do backups of our virtual machine workloads and azure.
Thanks for joining me today. I'm looking forward to seeing you in the next video