1 00:00:01,440 --> 00:00:02,150 In this demo, 2 00:00:02,150 --> 00:00:06,690 I'd like to add and initialize a new data disk to a virtual machine. 3 00:00:06,690 --> 00:00:08,870 So, we're looking here at my vm2, 4 00:00:08,870 --> 00:00:13,050 it's a Windows Server 2022 Datacenter box, and I'm going to come 5 00:00:13,050 --> 00:00:16,100 down to Disks, and we'll come down to Data disks, 6 00:00:16,100 --> 00:00:18,000 Create and attach a new disk. 7 00:00:18,000 --> 00:00:21,050 Now notice there's two options. I'm going to do a create, but we 8 00:00:21,050 --> 00:00:24,890 could also attach existing disks, but this would assume that you 9 00:00:24,890 --> 00:00:26,680 have some in your subscription. 10 00:00:26,680 --> 00:00:29,630 If you go up into the search and look for disks, 11 00:00:29,630 --> 00:00:33,710 you can get to the manage disks area here and you can create disks, 12 00:00:33,710 --> 00:00:38,450 you can upload VHDs from your on‑prem and then register them as disks. 13 00:00:38,450 --> 00:00:39,880 That's just another story. 14 00:00:39,880 --> 00:00:42,390 But what I'm going to do here is get rid of this entry 15 00:00:42,390 --> 00:00:45,180 because I'm not going to attach an existing disk, we're 16 00:00:45,180 --> 00:00:46,840 going to create a new one on the fly. 17 00:00:46,840 --> 00:00:50,550 And let's say that this is going to be a disk that will host database files 18 00:00:50,550 --> 00:00:53,100 and so it's going to need more predictable performance. 19 00:00:53,100 --> 00:00:57,960 I'm going to call this db‑files, and notice that for the storage type I can 20 00:00:57,960 --> 00:01:02,130 choose what type and what redundancy level I'm looking for here. 21 00:01:02,130 --> 00:01:06,520 I'm going to choose Premium SSD and then the size in gigabytes, 22 00:01:06,520 --> 00:01:08,740 I'm going to want that a lot bigger than 4, 23 00:01:08,740 --> 00:01:10,740 let's say 60 will do for now. 24 00:01:10,740 --> 00:01:14,380 And then we've got some other options that we don't need to get into right 25 00:01:14,380 --> 00:01:17,740 now about caching, and encryption, and so on and so forth. 26 00:01:17,740 --> 00:01:19,080 And once this is finished, 27 00:01:19,080 --> 00:01:23,550 this will allow us to sign into the VM and see this, well, once 28 00:01:23,550 --> 00:01:27,210 we initialize it we'll be able to work with this disk. Now, what 29 00:01:27,210 --> 00:01:30,680 about the question of resizing and making other changes? Well a 30 00:01:30,680 --> 00:01:32,140 lot of that has to be done, 31 00:01:32,140 --> 00:01:35,280 particularly if you're looking to do surgery on the OS disk, 32 00:01:35,280 --> 00:01:37,700 hopefully it makes sense that you're going to need to stop and 33 00:01:37,700 --> 00:01:39,920 deallocate the VM for that to work. 34 00:01:39,920 --> 00:01:42,860 But some of the controls that you see for OS in data 35 00:01:42,860 --> 00:01:44,580 disks, let me bring you in right there. 36 00:01:44,580 --> 00:01:47,560 You decide that you want to change the size of the disk. 37 00:01:47,560 --> 00:01:49,640 When we go to the Size + performance blade, 38 00:01:49,640 --> 00:01:52,430 we're going to see a number of stock‑keeping units, or SKUs, 39 00:01:52,430 --> 00:01:55,050 and we can change the disk type right here. 40 00:01:55,050 --> 00:02:00,100 Both Premium SSD, Standard SSD, which is meant to be a balance between 41 00:02:00,100 --> 00:02:04,690 the Premium SSD where you get full predictable speed at high cost, and 42 00:02:04,690 --> 00:02:07,380 the Standard HDD that's unpredictable, 43 00:02:07,380 --> 00:02:11,320 low speed at low cost. Standard SSD is a good compromise. 44 00:02:11,320 --> 00:02:16,100 But all three of these tiers come in discrete stock‑keeping units here, 45 00:02:16,100 --> 00:02:19,930 but note that you can come down and set a custom disk size and there's 46 00:02:19,930 --> 00:02:24,910 also various performance tiers that you can choose to boost or edit your 47 00:02:24,910 --> 00:02:28,850 throughput in your input/output operations per second. And notice that 48 00:02:28,850 --> 00:02:32,780 the blue up here says that Changes to the disk size can be made only 49 00:02:32,780 --> 00:02:36,990 when the disk is unattached or the managed virtual machine is 50 00:02:36,990 --> 00:02:37,800 deallocated. 51 00:02:37,800 --> 00:02:40,780 That means fully stopped and hardware deallocated. 52 00:02:40,780 --> 00:02:45,840 So I won't be able to actually change the size of the disk until I stop the VM. 53 00:02:45,840 --> 00:02:49,790 Let's finish up by just reviewing how we would initialize that new 54 00:02:49,790 --> 00:02:53,690 data disk. First, let me go back to the virtual machine disks page, 55 00:02:53,690 --> 00:02:55,390 make sure that it's still there, yes, 56 00:02:55,390 --> 00:02:58,310 it is, and then we're going to connect on the Overview page. 57 00:02:58,310 --> 00:02:59,630 Now later in this module, 58 00:02:59,630 --> 00:03:03,050 I'll show you more about Azure Bastion, but for now because 59 00:03:03,050 --> 00:03:06,150 I already have a bastion configured in my subscription, I'm 60 00:03:06,150 --> 00:03:07,830 going to do a Connect Bastion. 61 00:03:07,830 --> 00:03:11,020 This'll link up to the bastion that I've already created, and 62 00:03:11,020 --> 00:03:14,140 a bastion is simply a managed jump host. 63 00:03:14,140 --> 00:03:18,840 It allows you to connect over the internet on TCP 443 64 00:03:18,840 --> 00:03:21,730 using the encrypted HTTPS protocol. 65 00:03:21,730 --> 00:03:26,280 Sign in here, and that bastion runs exclusively in an HTML5 66 00:03:26,280 --> 00:03:30,340 browser. Supposedly the engineering team at Microsoft says that 67 00:03:30,340 --> 00:03:32,830 they'll support client applications eventually, 68 00:03:32,830 --> 00:03:36,860 but it's still just either an RDP desktop session or an 69 00:03:36,860 --> 00:03:39,770 SSH terminal session in a browser tab. 70 00:03:39,770 --> 00:03:41,370 It's better than nothing, for sure. 71 00:03:41,370 --> 00:03:44,810 So now we're here, I'm going to, I'm using a black wallpaper so it kind of 72 00:03:44,810 --> 00:03:50,170 hides it a little bit, I'm going to do a diskmgmt.msc, that's the shortcut 73 00:03:50,170 --> 00:03:53,970 file name to the Disk Management console, and the very first thing that 74 00:03:53,970 --> 00:03:56,340 pops up is this Initialize Disk. 75 00:03:56,340 --> 00:04:00,570 Are we going to use the old Master Boot Record or the new GPT? 76 00:04:00,570 --> 00:04:02,960 I'll go with MBR now and click Ok. 77 00:04:02,960 --> 00:04:06,310 Let's maximize our Disk Management console, and now we have 78 00:04:06,310 --> 00:04:10,570 our new 60GB disk online, but unallocated. 79 00:04:10,570 --> 00:04:13,570 So what we'll want to do is right‑click and create a New Simple 80 00:04:13,570 --> 00:04:17,040 Volume. Just like you would on‑premises, I'll use all the space 81 00:04:17,040 --> 00:04:19,820 and I'll give it the label db‑files, 82 00:04:19,820 --> 00:04:24,360 click Next, Finish, and before too long, I have my new drive 83 00:04:24,360 --> 00:04:27,020 available, and we'll have a drive letter before too long. 84 00:04:27,020 --> 00:04:28,420 Let me refresh the view. 85 00:04:28,420 --> 00:04:31,330 There we go, my drive E. So I can right‑click and 86 00:04:31,330 --> 00:04:35,820 explore my new Azure data drive. Oh, before I stop this demo, 87 00:04:35,820 --> 00:04:40,220 just to show you, here's that D drive, this is the temp disk, and it's a 16, 88 00:04:40,220 --> 00:04:44,640 for my VM size, it's only 16GB, and it's using solid state. 89 00:04:44,640 --> 00:04:48,260 If I right‑click and explore it, we're going to see that in 90 00:04:48,260 --> 00:04:51,360 Windows the D drive has this really scary message, 91 00:04:51,360 --> 00:04:55,500 DATALOSS_WARNING_README, and let's open up this text file just so you can 92 00:04:55,500 --> 00:04:59,480 take a look, I'll open it up in Notepad. And notice it says here, THIS IS A 93 00:04:59,480 --> 00:05:03,680 TEMPORARY DISK, all data stored on this drive is SUBJECT TO LOSS and THERE 94 00:05:03,680 --> 00:05:06,780 IS NO WAY TO RECOVER IT. And again, that's because your temp disk is 95 00:05:06,780 --> 00:05:11,550 attached to the hardware host and your VM may be live migrated at any time 96 00:05:11,550 --> 00:05:17,000 to a new hardware host. Let me close out of that Bastion session and call this demo done.