1
00:00:01,040 --> 00:00:05,760
Azure Site Recovery, or ASR. We examined Azure Site

2
00:00:05,760 --> 00:00:08,170
Recovery quite a bit in the previous module,

3
00:00:08,170 --> 00:00:12,000
but that was the backup and restore solution, and I had mentioned

4
00:00:12,000 --> 00:00:16,320
in that point that Azure Site Recovery has an entirely other part

5
00:00:16,320 --> 00:00:21,640
to it, and that is a replication‑based business continuity disaster

6
00:00:21,640 --> 00:00:24,130
recovery, or BCDR solution.

7
00:00:24,130 --> 00:00:27,230
So this is for protecting workloads, such that you can fail

8
00:00:27,230 --> 00:00:31,080
them over to another region or another data center or

9
00:00:31,080 --> 00:00:33,220
another disaster recovery V‑Net,

10
00:00:33,220 --> 00:00:36,840
there's plenty of different architectures, if you have a failure in

11
00:00:36,840 --> 00:00:40,880
your primary environment with not exactly 0 downtime,

12
00:00:40,880 --> 00:00:43,640
but a lot closer than what you'll attain in terms of

13
00:00:43,640 --> 00:00:47,930
recovery time objective than if you were doing VM backup and

14
00:00:47,930 --> 00:00:50,810
restore. Now, Azure Site Recovery,

15
00:00:50,810 --> 00:00:54,090
although it's mainly intended, by Microsoft anyway,

16
00:00:54,090 --> 00:00:57,650
it's mainly intended as a disaster recovery solution, and that's

17
00:00:57,650 --> 00:01:02,100
absolutely true, but originally many Azure customers used the Azure

18
00:01:02,100 --> 00:01:05,150
Site Recovery bits as a server migration solution.

19
00:01:05,150 --> 00:01:07,330
In other words, you configure replication,

20
00:01:07,330 --> 00:01:12,290
let's say, of your on‑premises Hyper‑V and VMware virtual machines into Azure,

21
00:01:12,290 --> 00:01:14,040
get them synchronized,

22
00:01:14,040 --> 00:01:18,030
create a failover where you cut over to the cloud, and then

23
00:01:18,030 --> 00:01:20,640
stop replication, and then you're done.

24
00:01:20,640 --> 00:01:22,140
And that's true, that works,

25
00:01:22,140 --> 00:01:25,740
but you should know that nowadays we have a fully fleshed out product in

26
00:01:25,740 --> 00:01:30,170
Azure that's called Azure Migrate Server Migration, and under the hood,

27
00:01:30,170 --> 00:01:34,060
though, it's interesting to tell you this, that the Azure Migrate Server

28
00:01:34,060 --> 00:01:37,970
Migration is, in fact, using Azure Site Recovery under the hood, it's just

29
00:01:37,970 --> 00:01:42,090
abstracted away. So, long story short, we see that Azure Site Recovery,

30
00:01:42,090 --> 00:01:46,110
both for the backup and restore stream, as well as the disaster

31
00:01:46,110 --> 00:01:50,340
recovery stream, allows us to protect our workloads in multi‑cloud

32
00:01:50,340 --> 00:01:55,170
environments, as well as hybrid‑cloud ones. And this is just basically

33
00:01:55,170 --> 00:01:57,590
a marketing infographic from Microsoft.

34
00:01:57,590 --> 00:01:58,240
As usual,

35
00:01:58,240 --> 00:02:02,220
we have the attribution link in the lower left corner of the slide that shows

36
00:02:02,220 --> 00:02:08,290
us some of the flexibility of ASR, that we can protect VMware and Hyper‑V

37
00:02:08,290 --> 00:02:11,940
virtual machines running both Windows and Linux.

38
00:02:11,940 --> 00:02:15,440
And we also have support for physical machines as well.

39
00:02:15,440 --> 00:02:17,130
You might think, well, how does that work?

40
00:02:17,130 --> 00:02:19,730
Well, if you were going to use ASR to replicate

41
00:02:19,730 --> 00:02:22,240
physical machines from on‑prem into Azure,

42
00:02:22,240 --> 00:02:26,100
hopefully it makes sense that in Azure those machines will run as VMs.

43
00:02:26,100 --> 00:02:29,520
Now you're not going to be able to fail back to a physical machine, but

44
00:02:29,520 --> 00:02:34,260
you could fail back to a VM on‑prem. This is for businesses that may be

45
00:02:34,260 --> 00:02:38,990
thinking of decommissioning that hardware and performing a P2V, physical

46
00:02:38,990 --> 00:02:41,210
to virtual conversion.

47
00:02:41,210 --> 00:02:43,640
ASR has got you covered with that. We also,

48
00:02:43,640 --> 00:02:46,330
as I mentioned, it's an Any OS situation,

49
00:02:46,330 --> 00:02:51,140
so we have support both for the Linux‑endorsed Linux distributions,

50
00:02:51,140 --> 00:02:53,940
as well as several versions of Windows Server.

51
00:02:53,940 --> 00:02:57,790
The topologies that you can realize with Azure Site Recovery are pretty

52
00:02:57,790 --> 00:03:03,640
powerful, and that is you can protect VMs, say, that are running in Amazon Web

53
00:03:03,640 --> 00:03:06,790
Services, and configure them to fail over to Azure,

54
00:03:06,790 --> 00:03:10,690
you see? Or you could do Azure to Azure. You could have your VM

55
00:03:10,690 --> 00:03:14,930
workloads running in your primary region, and then have the failover in

56
00:03:14,930 --> 00:03:17,530
another region so if there's a regional failure,

57
00:03:17,530 --> 00:03:19,980
you're still online. And then, of course,

58
00:03:19,980 --> 00:03:25,140
a very common solution is private cloud or on‑premises environment into Azure.

59
00:03:25,140 --> 00:03:33,000
So I just want you to see that ASR is very flexible in how you can configure and schedule disaster recovery.