1
00:00:01,840 --> 00:00:05,010
I want to repeat that aphorism that I was taught earlier in

2
00:00:05,010 --> 00:00:08,940
my IT career, that a good backup is only as valid as its

3
00:00:08,940 --> 00:00:10,940
ability to be successfully restored.

4
00:00:10,940 --> 00:00:14,990
I never ever want to see you in the situation where you're called upon in a true

5
00:00:14,990 --> 00:00:19,820
emergency to perform a restore and you realize, uh‑oh, I'm not as confident with

6
00:00:19,820 --> 00:00:24,280
this process as I would have been if I had done periodic restores. And even

7
00:00:24,280 --> 00:00:28,690
worse, I completed the restore, but I had something messed up in my backup

8
00:00:28,690 --> 00:00:31,340
settings and the restore is invalid.

9
00:00:31,340 --> 00:00:33,040
No, we don't want that.

10
00:00:33,040 --> 00:00:36,540
Now, what's our lead or our prompt for the next module?

11
00:00:36,540 --> 00:00:40,880
How about the issue of this hybrid cloud backup and

12
00:00:40,880 --> 00:00:43,810
restore solution is fine as far as it goes,

13
00:00:43,810 --> 00:00:45,840
but we have workloads running in Azure,

14
00:00:45,840 --> 00:00:49,360
let's say, or maybe hybrid, on‑prem, other clouds local

15
00:00:49,360 --> 00:00:51,900
that we cannot stand the downtime,

16
00:00:51,900 --> 00:00:56,700
which could be ours in terms of rebuilding that resource from a backup snapshot.

17
00:00:56,700 --> 00:01:00,540
What else is possible? And I had alluded to it a few times.

18
00:01:00,540 --> 00:01:04,260
This is called Azure Site Recovery, or ASR, and that's what

19
00:01:04,260 --> 00:01:06,980
we're going to do in the next module, implement disaster

20
00:01:06,980 --> 00:01:10,340
recovery by using Azure Site Recovery.

21
00:01:10,340 --> 00:01:14,000
Thanks very much. I look forward to seeing you then