Welcome back In this episode, we're gonna take some of the concepts learned the last episode and jump out into our azure portal for a naturist site recovery demo.
Our objectives include Just configuring has your sight recovery. Let's go over to the portal.
Here we are back in our answer portal. Let's go check out the recovery Service is and add a new recovery volt. Let's click on ADD Service is
search for recovery. Service is
first Selector. Resource Group.
I have one here called West US Recovery Volts.
Let's give the ball to name and keep the region as West us and let's finalize our creation
here in the overview page for our new vault, let's click on Replicate
and first we need to configure the source of our replication of our virtual machines. We have the options of azure or on premises. Right now, I'm only gonna be focused on our azure virtual machines for replication. Next, we need to select the source location of our virtual machines,
and first it comes up with West us. And as you can see in the warning here, you can't protect virtual machines
that are in the same region as the vault or the vault's resource group. The resource group that I created is also located in the West US, as is the recovery vault. So we need to select the source location that is different. In this case, my virtual machine is located in the East US. Next, we need to select the Source Resource Group,
which is gonna be the one called East U. S. V. EMS, where my virtue machines are located.
Next, we need to select the virtual machine that we want to replicate.
Here I have a virtual machine named East US Dash Win Dash BMO to This is a Windows Server 2016 server.
Finally, we have some additional settings we need to configure for our recovery vault. First is the target location of where we're going to send the replicated version machines.
We can also select a different subscription if we wanted to charge for it under a different building option.
Next kind of like our as your migrate scenario, we need to select the target resource group, network storage and availability options. This is just another regular virtue machine that needs to be configured like we would any other virtue machine
wheels of options for a replication policy of how often we want to create a recovery point and an application consistent snapshot. And finally, we can configure additional extension settings. I'm fine with all the settings I have here for this demo. So let's go ahead and create target resources
and we can enable replication.
Now enabling replication is going to take some time. You can see here I have V. M 01 already selected, and it's been synchronizing for probably 20 or 30 minutes. Now we'll wait for these to complete so we can perform a fail over
with a quick refresh and our portal here we conceive e M 01 is now protected, and V M O, to which we just configured for replication,
is starting to enter. Its protected state is currently at 0% synchronized.
Let's go take a look at V M o one's properties
here on the overview page, we can get a status of our replication health in the last R p o option that we have from here, we can perform a fail over and a test failure of the virtual machine again. As I mentioned the test veil over is going to check to make sure everything is configured correctly and the fellow are can occur.
Let's go ahead and skip that for right now and go ahead and perform a fail over.
Since we haven't performed a test fail over, we just have to click this. I understand box toe. Verify that we're taking a risk here by not performing that first.
Here you can see the Phil over direction. We're going from the East, us to the West us. And we have an option for a couple of different recovery points to choose.
The less processed has the lowest recovery time as it will revert to the virtual machine to the last recovery point that's in the site Recovery vault.
The latest has the lowest recovery point object,
which means it's gonna process any pending data in the site recovery service and then fell over. Or we can do a custom fail over where you can fail back to a particular recovery point. And if we were concerned about any app consistent, we have the latest app consistent option as well
for a person of this demo for a quicker recovery time, gonna click on latest processed.
You also have the option of shutting down the virtual machine before you begin. Fail over.
This is to help ensure that there is no data loss.
Even if the shutdown fails, the fail over will still occur.
I'm gonna select this option
and let's initiate our fail over
a refresh ever page shows our status is completing. Fail over. Let's go check this out.
We now see the fail over has completed successfully.
Let's go back to our vault.
Go back to our replicated items
we can now cr v m 01 has a status of a completed fell over.
Once a fail over is completed, our Veum should now be live in the West Years region. But this now means it's unprotected because it doesn't have a replicated VM back in the East US region
after the fail over is completed that you do have an option of re protecting it so it will replicate back to the primary region.
We select the more option
We can see our original resource group and virtual network of the original virtual machine.
we now see as you're working to re protect the original virtual machine in the primary region. If we refresh our page here, we can see the status has slipped back to enabling protection, Which means is going to start working on replicating the Verge machine back to the primary region.
Let's go back to the overview of our West U. S. Fault.
If we scroll down under monitoring, we can look at sight recovery jobs
and here we can see all the actions we've been taking and the current status of those replication and site recovery jobs.
Let's go into the re protect job of R V M 01
And here we can see the re protecting is still currently in progress.
While we're waiting on that to finish replicating back, I wanted to go take a look at our virtual machines and show you what we can see here.
Notice we have two verse machines with the same name. East us Dash win dash V M 01
and you can see the 2nd 1 here is currently running and it's in our ASR Resource Group over in the West US location.
This is showing that we have failed over to this first machine
as the name indicates it was originally created in the East US, but is now running. And the West us
The one above it is theory. Jinnah ll primary versus machine and is currently stop Andy allocated.
Going back and checking the status of our replication, We can see it is still enabling protection to start the replication process.
But failing back to the primary region is exactly like failing over to the secondary region. You'll just select the virtual machine and select, fail over and go through and configure the options of, like, fell over points. And if you want to shut down the virtual machine before failing over,
let's jump back over to our slide so we can wrap this up.
That does it for our recovery service. Is demo coming up next? We're gonna take a look at the other half of that with an Asher backup demo.
See you in the next episode.