Welcome back. In this episode, we're gonna discuss an introduction to azure site recovery.
Our objectives include understanding azure site recovery and then also understanding as your backup service is.
As always, let's ask the question. What is as your sight recovery as your sight recovery is all about business continuity and disaster recovery.
It is a service that keeps your workloads and business applications up and running during outages and its stores back up. Data for recovery,
as your sight recovery encompasses two different service is
the first is a sight recovery service. This is responsible for replicating your applications and virtual machines to another region in the event of a disaster outage. When the outage occurs in the primary site, you can fail over to the secondary location and access your workloads from there.
Once the primary is available again, you can fail back.
There's also the azure backup service is
this is responsible for keeping your data safe and recoverable like virtual machines.
This is similar how you might protect your servers on premises by utilizing a utility to backup files and applications on a server to disk or tape storage.
So let's talk a little bit more about the specifics of azure site recovery.
As your side recovery is an integral part of your business continuity and disaster recovery plan, it's responsible for orchestrating and replicating servers to another azure region.
You don't have to wait until there's a disaster to perform a fell over. You can use this service for maintenance events in order to keep your workloads running. And as your sight recovery also provides the ability tohave test runs to verify your fail over strategy is gonna be successful. What's really cool is as your sight recovery is not just for azure virtual machines.
You can also replicate on premises, first machines and physical servers in the data center.
This means you can take your own premises, servers and workloads and replicate them to azure for disaster recovery purposes.
There's no need to build another data center in another location. You can use Asher as your disaster recovery site,
and even if you do have a secondary data center, you can still use Asher site Recovery to replicate your on premises servers to that secondary data center through Azur.
I think that's pretty neat, don't you think? That's neat? And even on top of that you can take workloads over an Amazon Web service is our AWS and use azure as your recovery site. This introduces the idea of having a multi cloud strategy when it comes to cloud service Is Sai Recovery can also replicate several applications running on supported machines?
This includes workloads like active directory, Web, perhaps using I, I s and sequel
SharePoint exchange s AP Windows file servers and many more.
So we've been talking about azure side recovery for disaster recover scenarios. But we can also use it for migration.
If we look at our exam, eject IBS, it does list migrating servers to azure using azure site recovery. This is a different process than what we discuss in previous episodes.
He also remember from that episode I mentioned there was a previous version of the azure migrate tools.
In the previous version, it did not support migration of hyper V virtual machines. At the time, using azure site recovery was the only option for hyper V virtual machine migration.
Again, this is where I mentioned that exam objectives and test questions may not be 100% of today just yet with the cloud technology so understanding a few historical things in this case is going to serve you well on the exam.
This is why it's also important to review exam objectives before you sit for the exam, because they often do and list updates that are gonna be made to the objectives.
So you might be asking, what's the difference between using side recovery for business continuity and using it for migrations? It's actually pretty simple. You'd still set up replication from on premises machines to azure and perform a fail over. But once the Phil over is complete, you simply don't fail back.
If you're taking on premises servers to azure after the fail over is completed and workloads are verified, you a turnoff for decommission the on premises resource and just use the new one running in azure.
This process can also use if you want to migrate azure virtual machines from one region to another region or migrate and aws instance into azure.
Next, let's discuss as your backup. What as your backup does is pretty evident from his name. It provides backup service is utilizing the azure cloud.
Keeping with the theme of azure Recovery Service is as your backup is not just for azure virtual machines. You can also back up on premises, serves and workloads, thereby offloading any on premises backup solutions you might have hosted now.
But as your backup provides is apt, consistent, automatic and secure backup solution. You can back up a granular levels on the server, such as files, folders, machine system states and apple, where data backups.
You don't have to worry about expanding storage management or replication.
And you can use replication technologies like L R S R G RS, which is a concept we learned from our storage account discussions and earlier episodes.
And also you only have to pay for the storage that you use. So you might be asking yourself, Why would I use as your backup over as your sight recovery
as your backup provides data backup and recovery at a granular level?
Well, as your side recovery is for the entire server and requires failing it over
without your backup, you could just restore files, folders or machine system states instead of replicating the entire server before Mina fell over.
As your backup has a couple of different components, the first is a recovery service is vault
this fall is a resource that could be configured inside of most. Azure Resource is like virtual machines.
The recovery service vault must be in the same location or region as the virtual machines being backed up
via virtue machines and multiple regions. You'll need a vault in each of those regions.
The next component is a backup policy. This defines how backups are taken and how long they should be retained. You can set different retention periods for the daily, weekly, monthly and even yearly backups. And here on the right, we have a screenshot of what the backup policy looks like, and we'll take a further look at the's in our demo in the next episode.
Finally, there is the Mars Agent or the Microsoft Azure Recovery Service is agent.
This is used by as your backup to back up the files, folders and system state from on premises and as your servers,
it's responsible for sending the data to the Recovery service fault Inside of Azure.
You can also combine this agent with the on Premises Product System Center, data protection manager server. You can have the servers back up to this on premises server, then have the data protection manager back up to a vault and azure using the Mars agent
that does it for discussing an azure site recovery. And as your backup.
I think it's best in the next episode if we jump into a demo so we can look at how we configure the service's and get a better understanding of these concepts.
See you in the next episode.