1 00:00:01,140 --> 00:00:02,180 All right, good deal. 2 00:00:02,180 --> 00:00:03,550 So we're all set with that. 3 00:00:03,550 --> 00:00:07,340 Let's click Close, and now we can return to the Azure portal. 4 00:00:07,340 --> 00:00:07,710 All right, 5 00:00:07,710 --> 00:00:12,670 so now we're back in the portal. Let's refresh our view, and my win2019 6 00:00:12,670 --> 00:00:16,420 box is online, and registered, and all set to plug in. 7 00:00:16,420 --> 00:00:20,390 So let's now go over to Sync groups. And actually, before we do 8 00:00:20,390 --> 00:00:23,280 that, we want to make sure that we have a file share ready. I 9 00:00:23,280 --> 00:00:24,800 almost forgot that little detail. 10 00:00:24,800 --> 00:00:28,940 So let's head over to Azure Storage, and I'm going to pick on my 11 00:00:28,940 --> 00:00:33,730 timstorage001 storage account. We're going to come down under File 12 00:00:33,730 --> 00:00:40,730 shares, and I'm going to create a file share here called az801. Now, 13 00:00:40,730 --> 00:00:44,480 of course, that's kind of a ridiculous name in the real world, but 14 00:00:44,480 --> 00:00:48,180 just go with it. I want to make sure I can remember it is basically 15 00:00:48,180 --> 00:00:49,640 why I'm doing that. 16 00:00:49,640 --> 00:00:54,270 So there is our cloud‑based file share here in Azure Storage. Good to go. 17 00:00:54,270 --> 00:01:01,240 So let's come back to Storage Sync Services, ps‑storage‑sync, Sync groups, 18 00:01:01,240 --> 00:01:09,560 Sync group, and I'm going to call this scripts‑win2019. The storage account, 19 00:01:09,560 --> 00:01:14,440 let's browse to that right now, timstorage001, 20 00:01:14,440 --> 00:01:17,440 and then notice the reason why I wanted to make sure to go back and 21 00:01:17,440 --> 00:01:20,390 create that file share is that there is not an option to create 22 00:01:20,390 --> 00:01:23,540 one. It has to already be in existence. 23 00:01:23,540 --> 00:01:28,590 So we'll click Create to create that sync group. It's in the East US as 24 00:01:28,590 --> 00:01:32,490 well, and let's now go into the properties there, and we'll see it takes a 25 00:01:32,490 --> 00:01:36,730 little while for the one and only one cloud endpoint. Now the topologies 26 00:01:36,730 --> 00:01:39,640 that you can choose for Azure File Sync, 27 00:01:39,640 --> 00:01:41,980 it depends really. In other words, 28 00:01:41,980 --> 00:01:46,520 because we can have multiple server endpoints, we can bring in multiple 29 00:01:46,520 --> 00:01:51,030 paths. But notice that those local file share paths are going to 30 00:01:51,030 --> 00:01:54,680 resolve or be dumped into a single file share. 31 00:01:54,680 --> 00:01:58,050 So if you want to do a one‑to‑one mapping between local 32 00:01:58,050 --> 00:02:00,230 file shares and Azure file shares, 33 00:02:00,230 --> 00:02:02,700 you're going to have to create multiple sync groups. 34 00:02:02,700 --> 00:02:03,430 Otherwise, 35 00:02:03,430 --> 00:02:06,150 if you don't care, if you want to consolidate those local 36 00:02:06,150 --> 00:02:10,140 files into a single cloud endpoint, you can do that as well, 37 00:02:10,140 --> 00:02:11,840 totally up to you. 38 00:02:11,840 --> 00:02:14,280 So let's now go to, well, first of all, 39 00:02:14,280 --> 00:02:17,210 let me show you what happens, what options we have here. 40 00:02:17,210 --> 00:02:20,120 Basically, it's Properties and Delete for our cloud 41 00:02:20,120 --> 00:02:22,340 endpoint. Let's just take a quick look. 42 00:02:22,340 --> 00:02:25,760 So it looks like there's just a lot of metadata going on in the 43 00:02:25,760 --> 00:02:29,120 Resource ID. Not much you can do other than refresh and delete. 44 00:02:29,120 --> 00:02:33,300 Let's add a server endpoint in now, and we've registered our server, 45 00:02:33,300 --> 00:02:35,330 so we can choose it from the list. 46 00:02:35,330 --> 00:02:37,800 Now this takes a little bit of getting used to. The 47 00:02:37,800 --> 00:02:42,840 path needs to be a local path, not a universal naming convention path. 48 00:02:42,840 --> 00:02:46,380 So I'm going to want to come into my C drive, and I'm 49 00:02:46,380 --> 00:02:48,480 going to use scripts as my example here. 50 00:02:48,480 --> 00:02:50,570 So I'm going to copy that path. 51 00:02:50,570 --> 00:02:55,140 Of course, I could just type it, but I'm going to paste it in. 52 00:02:55,140 --> 00:02:58,740 We're not using Azure Data Box, so I'll ignore that. 53 00:02:58,740 --> 00:03:05,330 And then for Cloud Tiering, Disable or Enable. Now I have a faint 54 00:03:05,330 --> 00:03:09,810 recollection that cloud tiering doesn't work if your file share is on 55 00:03:09,810 --> 00:03:12,720 your C drive. We'll see if that happens. 56 00:03:12,720 --> 00:03:13,250 Okay, 57 00:03:13,250 --> 00:03:16,570 let's see. Here it is right here, actually. This is an 58 00:03:16,570 --> 00:03:19,440 exam alert point in real life as well. 59 00:03:19,440 --> 00:03:23,640 You may be trying to create a server endpoint using the system volume. 60 00:03:23,640 --> 00:03:27,410 Notice that cloud tiering does not work. Nuts! So I'm going to have to 61 00:03:27,410 --> 00:03:31,850 disable that. But you should know from an exam perspective, if you do 62 00:03:31,850 --> 00:03:34,950 enable cloud tiering that you're going to have to make sure that your 63 00:03:34,950 --> 00:03:38,270 local file paths are not on your C drive. 64 00:03:38,270 --> 00:03:41,350 And then also in addition to enabling tiering, 65 00:03:41,350 --> 00:03:46,830 you can specify here the percentage of volume free space via a policy. 66 00:03:46,830 --> 00:03:50,600 And this determines the aggressiveness of the tiering. 67 00:03:50,600 --> 00:03:51,370 In other words, 68 00:03:51,370 --> 00:03:54,900 20 is the default. That says make sure that you're 69 00:03:54,900 --> 00:03:56,840 reserving, or Azure File Sync, 70 00:03:56,840 --> 00:04:01,950 make sure that you're reserving at least 20% of free space on that volume. 71 00:04:01,950 --> 00:04:04,320 So the higher you make this percentage, 72 00:04:04,320 --> 00:04:08,300 the more free space you'll have locally, but the more aggressive the tiering 73 00:04:08,300 --> 00:04:14,450 will be, you see? And we also can specify a date policy, only cache files that 74 00:04:14,450 --> 00:04:18,650 were accessed or modified within a certain number of days. So these are our 75 00:04:18,650 --> 00:04:22,770 controls to adjust that level of aggressiveness, all right? Let's see, for 76 00:04:22,770 --> 00:04:28,110 initial sync, this determines how gentle you want that initial upload to be. 77 00:04:28,110 --> 00:04:32,780 Merge the content of the server path with the content in the Azure file share. 78 00:04:32,780 --> 00:04:37,640 Files with the same name and path will lead to conflicts, or we can 79 00:04:37,640 --> 00:04:42,900 authoritatively overwrite any conflicted files in the Azure file share. I'm 80 00:04:42,900 --> 00:04:46,410 going to choose Merge, and then we have download. Now you might wonder, if 81 00:04:46,410 --> 00:04:50,370 you're doing cloud tiering, that means that you're going to be able to enumerate 82 00:04:50,370 --> 00:04:54,940 files locally, but the file may not actually be available locally. 83 00:04:54,940 --> 00:04:58,690 So that means the first time the file is requested, it 84 00:04:58,690 --> 00:05:01,950 will need to be recalled from the server. 85 00:05:01,950 --> 00:05:04,980 So here, you're adjusting how that is going to happen when you're 86 00:05:04,980 --> 00:05:08,290 doing cloud tiered. Download the namespace first, 87 00:05:08,290 --> 00:05:12,250 then recall the file content as much as will fit, or download the 88 00:05:12,250 --> 00:05:16,300 namespace, file content will be recalled when accessed. That option would 89 00:05:16,300 --> 00:05:19,410 only be applicable if you are, in fact, using tiering, 90 00:05:19,410 --> 00:05:21,510 which I cannot do in this case. 91 00:05:21,510 --> 00:05:25,660 Let me click Create. And that's really, believe it or not, all there is to 92 00:05:25,660 --> 00:05:29,900 it. Largely, it's just self‑running and self‑maintaining. 93 00:05:29,900 --> 00:05:32,680 So once that server endpoint is provisioned, 94 00:05:32,680 --> 00:05:36,210 there's going to be that initial sync, and then from now on, 95 00:05:36,210 --> 00:05:39,780 you've just got that synchronization taking place based on the 96 00:05:39,780 --> 00:05:42,350 properties that you've set. And again, 97 00:05:42,350 --> 00:05:46,510 all you can do from the server endpoint from a configuration standpoint is 98 00:05:46,510 --> 00:05:51,720 get back to your properties and delete the endpoint. So you can see here 99 00:05:51,720 --> 00:05:55,040 there's some metrics charts that we can look at. 100 00:05:55,040 --> 00:06:00,240 Let me step back out of that full‑screen view and go back to the sync group. 101 00:06:00,240 --> 00:06:03,010 But just by way of quick glance, 102 00:06:03,010 --> 00:06:05,610 the two metric views you have are the number of 103 00:06:05,610 --> 00:06:08,590 files synced and then the volume, 104 00:06:08,590 --> 00:06:11,780 the bytes synced. It will take a little while for this to kick in, 105 00:06:11,780 --> 00:06:15,770 but eventually, we'll be able to monitor it. After about 10 minutes 106 00:06:15,770 --> 00:06:22,360 or so, we see the data showing up here, so it looks like 18 uploads, 1 download, 107 00:06:22,360 --> 00:06:28,000 so we can just follow that, and we can make alerts, etc, etc. There you have it.