1
00:00:01,140 --> 00:00:05,130
It looks like this is just giving us the configuration fragment

2
00:00:05,130 --> 00:00:09,710
that we could pass in or construct maybe a full ARM template

3
00:00:09,710 --> 00:00:13,040
based on this configuration fragment.

4
00:00:13,040 --> 00:00:16,440
If we take the azuredeploy JSON that was created,

5
00:00:16,440 --> 00:00:20,140
let me right‑click and open that in VS Code as well,

6
00:00:20,140 --> 00:00:24,830
yes, here is the full template that would allow us to deploy a VM,

7
00:00:24,830 --> 00:00:29,440
a new VM based on those disk snapshots in the backup here.

8
00:00:29,440 --> 00:00:31,490
And if we take a look in VS Code,

9
00:00:31,490 --> 00:00:35,210
if I open up Explorer and bring out my ARM template outliner,

10
00:00:35,210 --> 00:00:39,970
that'll allow us to browse the template file a bit easier,

11
00:00:39,970 --> 00:00:44,560
and in order to get the ARM template outliner in VS Code and to be

12
00:00:44,560 --> 00:00:47,420
able to work with ARM schemas and ARM templates,

13
00:00:47,420 --> 00:00:50,930
you'll want to make sure to go to the Extensions blade and

14
00:00:50,930 --> 00:00:53,640
load in the Azure Resource Manager Tools,

15
00:00:53,640 --> 00:00:56,140
or ARM Tools extension from Microsoft.

16
00:00:56,140 --> 00:00:59,520
It's a very important extension indeed when you're doing

17
00:00:59,520 --> 00:01:01,980
ARM deployment template work in Azure.

18
00:01:01,980 --> 00:01:04,710
Whoops, I didn't want to leave the outliner here.

19
00:01:04,710 --> 00:01:08,680
Let's go to Resources, we've got our virtual machine,

20
00:01:08,680 --> 00:01:12,740
and again, all of our configuration and all of that stuff here.

21
00:01:12,740 --> 00:01:12,950
Yeah,

22
00:01:12,950 --> 00:01:16,500
and we can see a reference to those managed disks here on

23
00:01:16,500 --> 00:01:19,890
Line 92 that when we do this deployment,

24
00:01:19,890 --> 00:01:26,340
we would attach that disk from the managed disks library in our subscription.

25
00:01:26,340 --> 00:01:30,180
I wanted to show you here, I've got a full backup of a Linux virtual machine.

26
00:01:30,180 --> 00:01:32,130
If I go to File Recovery,

27
00:01:32,130 --> 00:01:35,080
I just want to demonstrate that the process here is just about

28
00:01:35,080 --> 00:01:38,590
exactly the same for a Linux VM as it is an Azure one,

29
00:01:38,590 --> 00:01:41,360
it's just that the script uses a different language.

30
00:01:41,360 --> 00:01:46,860
We choose our recovery point, whatever that is, then we download a script.

31
00:01:46,860 --> 00:01:52,040
The portal will generate a Python script with a one‑time password.

32
00:01:52,040 --> 00:01:55,510
You open up a terminal, execute the Python script,

33
00:01:55,510 --> 00:01:56,960
unlock with a password,

34
00:01:56,960 --> 00:01:59,680
and then you've got a mount operation that happens

35
00:01:59,680 --> 00:02:06,000
just like in a Windows environment. Same thing, same process, it's just using a different engine.