1
00:00:00,840 --> 00:00:04,930
In this demonstration, we'll go a bit further with Azure File Sync service.

2
00:00:04,930 --> 00:00:05,880
As you can see,

3
00:00:05,880 --> 00:00:10,130
we're in our storagesyncservice that I created in the previous module,

4
00:00:10,130 --> 00:00:13,650
and on the Overview page, this is a shortcut to my sync groups.

5
00:00:13,650 --> 00:00:16,640
I've created some additional sync groups since last time.

6
00:00:16,640 --> 00:00:20,960
I still have just the one local file server in my Registered servers list.

7
00:00:20,960 --> 00:00:23,990
It's a Windows Server 2022 machine that has the most

8
00:00:23,990 --> 00:00:26,640
recent version of the AFS agent on it.

9
00:00:26,640 --> 00:00:30,270
Let's go over to Sync groups and I'll show you about cloud tiering first of all.

10
00:00:30,270 --> 00:00:34,990
I have a sync group called reports, let's go and inspect its properties,

11
00:00:34,990 --> 00:00:41,110
that's mapping to a file share called reports in my contoso storage account.

12
00:00:41,110 --> 00:00:43,980
And this is a good place to see, first of all,

13
00:00:43,980 --> 00:00:47,800
the resource ID and the storage account name and all of that,

14
00:00:47,800 --> 00:00:49,500
of where the cloud endpoint is,

15
00:00:49,500 --> 00:00:52,530
but you can also see Change Enumeration down there.

16
00:00:52,530 --> 00:00:55,770
That can be particularly useful from a quantitative point of view.

17
00:00:55,770 --> 00:01:01,290
Down here we have our server endpoint, and notice that the path is e:\reports.

18
00:01:01,290 --> 00:01:03,390
That's important if you're going to do cloud tiering.

19
00:01:03,390 --> 00:01:04,650
Let me show you what I mean.

20
00:01:04,650 --> 00:01:08,190
By the way, this is a good report here, this Cloud Tiering report.

21
00:01:08,190 --> 00:01:11,030
When you enable cloud tiering on a server endpoint,

22
00:01:11,030 --> 00:01:14,680
you can see your space savings and what files are cached,

23
00:01:14,680 --> 00:01:18,790
what files are not. And the two policies that I had mentioned earlier

24
00:01:18,790 --> 00:01:22,780
about how the cloud tiering actually behaves, you've got your Volume

25
00:01:22,780 --> 00:01:25,440
Free Space Policy and your Date Policy.

26
00:01:25,440 --> 00:01:30,400
Volume Free Space is going to be a percentage of the volume on which you're

27
00:01:30,400 --> 00:01:33,660
associated shared folder is. It's not the shared folder.

28
00:01:33,660 --> 00:01:36,770
You want to think about the overall size of the volume.

29
00:01:36,770 --> 00:01:41,600
So if the volume were, let's say, 100 GB and you set this to 20,

30
00:01:41,600 --> 00:01:46,730
that's telling Azure File Sync that you always want at least 20 GB

31
00:01:46,730 --> 00:01:50,630
free space and that would adjust the aggressiveness of the file

32
00:01:50,630 --> 00:01:52,960
offloading process up into the cloud.

33
00:01:52,960 --> 00:01:57,680
You can also do a Date Policy, and this says Only cache files that were

34
00:01:57,680 --> 00:02:02,520
accessed or modified within the specified number of days, and by cache we

35
00:02:02,520 --> 00:02:07,320
mean keep a copy of the files on the local registered server as opposed to

36
00:02:07,320 --> 00:02:11,450
being offloaded into the cloud. And you'll find over time, I don't think

37
00:02:11,450 --> 00:02:15,460
it's happened yet in my case because I just set this up, but if we look at

38
00:02:15,460 --> 00:02:17,270
the properties of a file,

39
00:02:17,270 --> 00:02:21,580
one way to quickly eyeball that it's actually been offloaded into tiered

40
00:02:21,580 --> 00:02:24,790
storage is that the size on disk will show up as 0.

41
00:02:24,790 --> 00:02:28,050
Again, another place from a monitoring perspective is right here in the

42
00:02:28,050 --> 00:02:32,010
Server Endpoint Properties we can see the tiering efficiency. Of course, we

43
00:02:32,010 --> 00:02:34,810
can also get to that from Azure Monitor as well.

44
00:02:34,810 --> 00:02:38,940
Now the point here that I wanted to make also with cloud tiering is that

45
00:02:38,940 --> 00:02:42,770
it does not work on system volume, so you'll want to make sure that if

46
00:02:42,770 --> 00:02:45,490
you do plan to do cloud tiering on a share,

47
00:02:45,490 --> 00:02:52,000
that share needs to be not on drive C. Here we can see from a monitoring perspective.