馃攳
Business Continuity with Azure - Disaster Recovery - YouTube
Channel: unknown
[2]
[Music]
[8]
hi everybody and welcome to this
[10]
business continuity with azure series
[12]
today we're going to be talking about
[13]
disaster recovery
[16]
the disaster recovery is a process of
[18]
bringing bringing your i.t systems back
[20]
up and running
[21]
after something has happened either that
[23]
be a natural disaster or a human
[25]
induced disaster now looking at the
[28]
research there's a number of reasons
[29]
that we have those disasters or
[31]
disruptions with our systems
[33]
the most significant one is a systems
[35]
failure something is broke or isn't
[37]
working the way that it should do
[39]
the second one is a power failure again
[42]
whether that be something that
[44]
um has failed or maybe it could be
[46]
someone has been drilling out in the
[47]
street outside and caused that issue for
[50]
you
[51]
the third one is a natural disaster some
[54]
kind of weather element has
[55]
impacted your data center and knocked
[57]
out your i.t systems
[58]
and the last one is cyber attacks
[61]
someone is
[62]
trying to maliciously get into your
[63]
system and has caused an outage
[66]
nutella when traders currently have
[68]
their own data center and they rent
[70]
a space in a co-location data center and
[72]
they use that for the disaster recovery
[74]
space
[75]
their setup is fairly simple fairly
[77]
straightforward and probably fairly
[78]
familiar with you
[80]
they have that's that primary site in
[82]
glasgow and they use a third-party
[84]
software to replicate their data and
[86]
their applications
[87]
across to more kept more hardware in a
[90]
co-location space in edinburgh
[92]
which is about 46 miles away from them
[95]
so if there was some kind of weather
[96]
element or a power failure in glasgow
[99]
it hopefully wouldn't be affecting
[100]
edinburgh and they can bring everything
[102]
back up there
[103]
the tailwind traders are looking at
[105]
renewing that contract so their
[107]
co-location provider contract is up
[109]
and they're not sure whether to renew
[111]
that or looking at
[113]
an alternative now they've not really
[115]
given us any criteria
[117]
and around what they're going to use to
[119]
evaluate the alternatives but they want
[120]
to
[121]
get some proposals in so i'm going to
[123]
propose that they look at using azure
[125]
and azure site recovery instead
[128]
now with azure site recovery we have the
[130]
ability to
[131]
take that those applications all that
[133]
data copy it from on-prem and put it up
[136]
into azure so
[137]
azure becomes that secondary recovery
[139]
site for them
[140]
and azure site recovery becomes that
[142]
kind of replication software that does
[144]
all of that for them and can trigger
[146]
um the disaster recovery now it gives us
[149]
the ability to set up our rtos
[152]
or rpos which are recovery time
[154]
objectives and recovery point objectives
[156]
and we have the ability to kind of
[157]
flexibly do what we need and to make 21
[160]
traders confident with this solution
[162]
we also have the ability to actually
[165]
test the disaster recovery plan we can
[167]
implement
[168]
a drill that doesn't actually deal with
[171]
any of the production workloads so we
[172]
can work through the processes refine it
[175]
and make sure everybody understands
[176]
what their role is during a disaster
[178]
recovery and what they need to do
[182]
we also have the ability to create those
[184]
application consistent snapshots which
[185]
are super important for a lot of
[187]
applications
[188]
so for example if you're using microsoft
[190]
sql and there's often some pending
[192]
rights that are happening within memory
[194]
and the application consistent snapshots
[196]
can help capture all of that and make
[198]
sure that when you do bring up the
[199]
application
[200]
in the secondary site that all of that's
[202]
captured and
[203]
and and should be where is and lastly
[207]
we have the ability to actually automate
[209]
some of the process
[211]
um so often you can have these complex
[213]
procedures for your disaster recovery
[215]
plan whether that be re-iping a bunch of
[217]
servers or starting up some services
[220]
in a certain order we can create a
[222]
script and then implement that with
[224]
azure automation so that kind of takes
[226]
out that human element so we can
[228]
try and mitigate against anybody
[230]
accidentally typing the wrong thing or
[231]
starting the wrong service at the wrong
[233]
time
[234]
and make the process much more
[236]
streamlined for everybody
[238]
now again the solution is a bit
[240]
simplified and we can do away with that
[242]
secondary site in edinburgh we don't
[244]
have to pay that co-location and we can
[246]
get rid of the hardware or utilize it
[248]
somewhere else and then we use azure
[250]
site recovery on-prem
[251]
to replicate everything up into azure
[253]
and azure becomes that secondary site
[256]
for them
[257]
now doing this there's a bunch of
[259]
benefits to tailwind traders
[261]
like i said the complexity of protecting
[264]
those data and applications can be taken
[266]
away
[266]
and we can also take away some of the
[268]
complexity when we're bringing
[270]
everything back up by using scripts and
[272]
automation
[273]
we can also deal with a large amount of
[275]
data that you may have that tailwind
[276]
traders may have on prem
[278]
we can scale that and azure to a certain
[280]
extent
[281]
we can also deal with any of the
[283]
long-term um data retention requirements
[285]
that tailwind traders have
[287]
again we have that depth in that breadth
[289]
of protection built into azure site
[290]
recovery and
[291]
azure and we have that test bed so that
[294]
we can work through everything we can
[296]
work through the disaster recovery plan
[298]
anything changes on prem we can we can
[301]
replicate that change up and then work
[303]
through it and make sure the
[304]
documentation and the processes
[306]
are all ingrained and all set out for
[308]
everybody
[310]
and we can possibly make some savings
[312]
around this so at the moment as i said
[313]
they pay for the contract
[315]
they pay for the rent of that
[316]
co-location space and they've also
[318]
invested a bunch of
[319]
money into hardware for that co-location
[322]
space
[322]
and that's sitting doing nothing most of
[324]
the time so we can maybe
[325]
save some money by utilizing azure site
[328]
recovery and azure as well
[331]
so you want to learn more about azure
[333]
site recovery or disaster recovery with
[335]
azure
[336]
if you head over to our documentation
[337]
and go to aka dot ms
[339]
bc recovery we can you can read about
[342]
azure site recovery and the processes
[344]
around all of that
[346]
we also have a module within ms learn
[348]
where you can learn about disaster
[350]
recovery
[351]
and site recovery and how you can
[352]
implement that as well
[355]
thank you for watching and hopefully
[356]
we'll catch you on another one of these
[358]
videos
[359]
thank you
Most Recent Videos:
You can go back to the homepage right here: Homepage