today we will take a look at how as your
site recovery can help you to keep your
applications available in the event of a
disaster I'll show you how you can set
up replication for your on-premises
applications and how you can test the
solution works in the event of a
disaster
to meet your compliance fees if you are
new to Azure site recovery it is a
service that allows you to replicate
your application bill over to Azure so
that you can plan for and enable
business continuity let me show you how
you can go about setting up your
on-premises data center with disaster
recovery in Azure here I have a VMware
ESX farm running in my data center
I have Linux virtual machines running
Apache and my sequel there are a few
steps you'll have to take to connect
your on-premise environment to Azure and
to replicate your applications which
I'll show you in another tenant the
first thing you will need to do in Azure
is create a recovery services vault
this holds your settings monitoring and
reports policies protected items the
management plan for the resources that
you are managing as well as your site
recovery plan here I have a number of
volts created to create a new one I
click add and there are a number of
steps that I need to complete in order
to finish creating my recovery services
vault in my case I've already created
one but once you've created your
recovery service as well there are three
main steps to set up as your site
recovery preparing your local
infrastructure replicate your
applications and preparing your recovery
plan let's get started with preparing
your local infrastructure to do this I'm
going to click my recovery services
vault that I want to set up site
recovery for under getting started I'm
going to select site recovery next
prepare infrastructure I will set my
protection goal of replicating
applications on-premises to Azure on
VMware virtual machines and click OK
to orchestrate the connectivity between
our on-premise environment I'm going to
add the center I'm going to enter my
host friendly name the host account from
the drop down menu and click OK next I'm
going to select replicate applications
and select my source for configuration
which will be on-premises I will
complete a couple steps ending with
selecting my process server and clicking
ok next I'll select the configuration
target for where I want my applications
to run in Azure I'll select virtual
machines configuration properties and
replication settings my last step is to
manage my recovery plan this is where
you can customize your recovery plan and
test for failover
without impacting production workloads
or end users to customize this means
that I can sequence the failover
multi-tier applications running on
multiple VMs to get more detail on all
of these steps you can check out the
link below now let me show you the
experience once you've passed the setup
stage in my original environment that
I've already set up you can see here
that Asscher is now directly connected
to my V Center instance on-premises if I
look at the replicated items you can see
that the 5 Linux virtual machines that I
showed you earlier are now set up now
I'm going to go to my recovery plan and
I'm going to select Customize this is
where you can determine what needs to
happen and in what order for failover to
work in this case I've customized my
recovery plan so that my sequel database
needs to be running before group 2 which
is the apt here which needs to come up
before group 3 which is the web tier
when I go to group 4 you can see that I
have a public-facing internet IP this
enables me
to turn on virtual machines in a
specific order and then run scripts
because I have set up my recovery plan I
can do a single click failover and it
will execute these items to give you a
peace of mind we allow you to test that
your recovery plan will work in the
event of a disaster and meet your
compliance needs without impacting your
production environment or end-users so
let's go ahead and simulate an outage
there could be many reasons for an
outage ranging from a natural disaster
to human error in this case let's assume
an outage it's due to human error by
shutting down our VMware ESX VM to do
this I'm going to hit power shutdown and
it's going to ask me if I really want to
shut this down I'm going to click OK
this will bring down services reliant
upon those VMs within our public website
so if I hit refresh we'll see that the
site is down now the test failover I'll
go back to the azure portal and I'll
choose failover and I'm going to select
my latest application consistent
recovery point that's the last state of
our services and applications and choose
ok this is going to kick off the
recovery services process you can see
here the recovery is moving forward and
because our recovery process is
sophisticated it will take a few minutes
to spin once it's complete you'll be
able to see that your applications are
running and when we refresh our website
our website is back in running we've
successfully recovered from the outage
getting started with as your site
recovery is easy it's built into Azure
so as long as you have and as your
subscription you can get started today
and it's free to use for the first 31
days also the azure hybrid use benefit
allows you to apply existing Windows
Server licenses towards this effort you
can learn more about this benefit on a
recent demo fetch and for detailed
documentation and how to get started
with Azure site recovery you can visit
the links below thanks for watching
[Music]