馃攳
Azure Essentials: Business continuity and disaster recovery - YouTube
Channel: Microsoft Mechanics
[4]
- Welcome to Azure Essentials,
[6]
in the next few minutes
I'll walk you through
[7]
how you can use Azure's
global cloud platform
[9]
to keep your business-critical
services up and running,
[11]
and to protect and restore
your data from a specific point
[14]
in time as part of a business continuity,
[16]
disaster recovery plan
for your organization.
[19]
In Azure, there are two core services
[20]
that you'll wanna take advantage of.
[22]
The first is Azure Site Recovery, or ASR,
[24]
and the second is Azure Backup.
[26]
Both ASR and Azure Backup
complement each other
[28]
to provide you with an
end-to-end business continuity
[31]
and disaster recovery
solution with unlimited scale.
[34]
In the case of an outage,
this allows you to recover
[36]
your business services in a
timely and orchestrated manner,
[39]
and safeguards the recovery of your data
[41]
in the event of accidental deletion,
[43]
corruption, and even ransomware.
[45]
With ASR you can replicate Azure VMs
[48]
between Azure regions,
or you can replicate
[50]
on-premises VMs, physical
servers to Azure.
[53]
In this case, Azure Site
Recovery will coordinate
[56]
virtual machine and
physical server failover,
[58]
from your primary site to
Azure, and can fail back
[61]
to the primary location
once it's running again.
[64]
Additionally, Azure Site
Recovery integrates with
[66]
other business continuity and
disaster recovery services.
[69]
For example, it can protect your important
[71]
SQL server workloads by
managing the failover
[73]
of SQL server AlwaysOn
availability groups.
[76]
ASR offers best-in-class
Recovery Time Objectives, RTO,
[80]
and Recovery Point Objectives,
RPO, so if your service
[83]
goes down, it can be back up in minutes.
[86]
Application-consistent
snapshots which capture
[88]
disk data, and transactions in process,
[90]
are mapped to your
specified recovery points
[93]
to keep your apps
consistent during failover.
[96]
You can also customize
the orchestration sequence
[98]
for the failover and
recovery of multi-tier
[100]
applications, running on multiple VMs.
[102]
Recovery steps can be automated
[104]
by taking advantage of our
Azure Automation Library
[106]
of application-specific scripts.
[108]
Additionally, you can
use your own scripts,
[111]
or opt to manually initiate
recovery from the Azure portal.
[114]
You can also customize
the orchestration sequence
[116]
for your failover and
recovery of multi-tier
[118]
applications running on multiple VMs.
[120]
ASR uses the network management
capabilities in Azure,
[123]
such as reserving IP addresses,
[124]
and controlling load balancers,
[126]
and can be used with Azure Traffic Manager
[128]
for efficient network switch-overs.
[130]
Moving on to Azure Backup as part of your
[132]
business continuity and
disaster recovery plan,
[134]
you can ensure that your important data
[135]
is backed up whether it lives on-premises,
[137]
or in the cloud, and you can configure
[139]
the service to your specific
recovery point objectives.
[142]
Based on your goals, Azure Backup takes
[144]
multiple snapshots of
your data to give you
[146]
the flexibility to restore your business
[148]
back to a specific period in time.
[151]
For example, you can ensure that your
[152]
database is backed up every 15 minutes,
[154]
or that your VMs are backed up daily.
[157]
If you've got VMs running
in Azure, you can configure
[159]
backup and retention
schedules to recover your VMs
[161]
as well as their content,
such as files and folders.
[164]
The backups are application-consistent
[166]
in nature, and you don't need any
[168]
additional infrastructure
for this to work.
[170]
If, on the other hand,
you're looking at backing up
[172]
your on-premises resources,
Azure Backup gives you
[174]
a wide variety of backup options.
[176]
You can, for example, just
choose to do a general backup
[179]
of your Hyper-V and
VMware virtual machines
[181]
from your datacenter, and
even capture system state
[184]
on your physical machines through
[185]
a bare metal recovery, if needed.
[187]
Equally, you can choose to back up
[189]
your files and folders or the data
[191]
in specific workflows, such
as Exchange email data,
[193]
data stored in SQL, or in SharePoint.
[196]
To understand more about
your backup options,
[198]
it's a good idea to refer
to the Azure Backup server
[200]
protection matrix which also
details known constraints.
[204]
Once your data is copied to
Azure, it will synchronize
[206]
only delta changes, saving you time
[208]
and internet connection
charges, and it can even
[210]
ship your data offline
to the Azure Datacenter
[212]
hosting your backup, if that's preferable.
[215]
The data is encrypted
in transit and at rest,
[217]
and you as the customer
hold the encryption keys.
[220]
With your data backed up
in Azure, you can also
[222]
take advantage of additional
built-in protections.
[225]
For example, we know that
most ransomware attacks
[227]
typically attempt to gain
control of your backup process
[230]
by deleting previous data backups.
[232]
To help mitigate this threat,
when you set up Azure Backup
[234]
you can configure your
Recovery Services vault
[236]
for multi-factor authentication.
[238]
This ensures that a security PIN
[240]
is generated to perform
critical operations
[242]
such as updating or
removing a recovery point.
[245]
So now let's talk a
little bit about setup.
[247]
I just showed you the
Recovery Services Vault,
[249]
and this is an important point,
both services require you
[252]
to set up a Recovery Services
Vault to hold your settings,
[255]
monitoring and reports,
policies, protected items,
[258]
and site recovery plan
as well as backup items,
[260]
backup jobs, and backup usage logs.
[263]
Next, you'll follow a
step-by-step wizard experience
[266]
that walks you through the
information needed to ensure
[268]
that your environment replicated,
and your data protected.
[272]
For ASR, this includes
setting a target where
[274]
your application will land in Azure,
[276]
the virtual machines
you want to replicate,
[278]
as well as preparing your recovery plan.
[279]
For Azure Backup, if you're
backing up from Azure,
[282]
you just need to select the VM resources
[284]
that you wanna backup, and
in a few steps you're done.
[287]
The steps include
selecting your backup goal,
[288]
the frequencies of your
backup, and how long
[290]
you wanna retain the backups
to meet compliance purposes.
[293]
If, on the other hand,
you're backing up your
[295]
datacenter resources, you need to choose
[297]
the on-premises data sources
that you wanna backup
[299]
to Azure, and prep your
on-premises infrastructure.
[303]
Storage for your protected
data comes in two flavors.
[305]
LRS is a low-cost option
for protecting your data
[308]
from local hardware failures in Azure.
[310]
GRS, on the other hand, provides
[311]
a higher level of
durability for your data,
[314]
even if there's a regional outage.
[316]
You only pay for the
storage that you consume.
[318]
For the specific prerequisites,
and to learn more
[320]
about the setup experience,
visit the links shown.
[323]
Of course, before you
set up these services,
[325]
getting the most effective use
of Azure to handle the backup
[327]
of your services and
data takes some planning.
[330]
For Azure Backup, data's
kept by default for 30 days,
[333]
so you'll want to extend
this period to support
[335]
your specific data
retention goals, which could
[337]
be many years, to meet your
regulatory requirements.
[340]
For ASR on the other hand,
you'll need to determine
[342]
which VMs to replicate by assessing
[344]
the impact to your business,
if the specific apps
[346]
and workflows that you
run experience downtime.
[349]
To support deployment planning,
[350]
the Site Recovery Deployment
Planner is a command line tool
[353]
that allows you to
remotely profile your VMs
[356]
to understand the bandwidth
and storage requirements,
[358]
for successful replication of failover
[360]
based on your recovery point objectives.
[363]
You can run the tool without installing
[364]
any site recovery components on-premises,
[366]
and it also gives you an estimated
[368]
disaster recovery cost
for failover to Azure.
[370]
As you shift to manage failover
and data backup with Azure,
[373]
you also benefit from
built-in monitoring tools.
[376]
In Azure Site Recovery,
out-of-the-box monitoring
[378]
helps you to continually oversee your
[380]
business continuity
objectives, you can also choose
[382]
to receive email notification
for critical events
[385]
so that you're able to
proactively address any issues
[387]
that might impact your ability
to react to a disaster.
[390]
Furthermore, in Azure
Backup, the vault dashboard
[393]
gives you visibility into the
list of backup jobs, alerts
[396]
for failed backup jobs, restore
jobs, and delete operations.
[400]
Similarly, you can set up
email notifications for alerts,
[402]
or push monitoring data to
a Log Analytics workspace,
[405]
or PowerBI for a holistic view
[407]
across all of your Azure subscriptions.
[409]
So that was an overview
of how you can use Azure's
[411]
global cloud platform to keep your
[413]
business-critical services up and running,
[415]
and to protect and restore
your data from a specific
[417]
point in time as part
of a business continuity
[419]
and disaster recovery plan
for your organization.
[422]
Azure Site Recovery and Azure
Backup are built into Azure,
[425]
so if you have an Azure subscription
[426]
you can get started today, and ASR
[428]
is free to use for the first 31 days.
[431]
And, of course, to learn more about Azure
[433]
and to get access to additional
[434]
learning resources,
please keep checking back
[436]
on Azure Essentials at the link shown.
[438]
Thanks for watching.
Most Recent Videos:
You can go back to the homepage right here: Homepage