1
00:00:01,140 --> 00:00:04,590
Cloud tiering is another advantage of the Azure File Sync service.

2
00:00:04,590 --> 00:00:04,820
Here,

3
00:00:04,820 --> 00:00:08,420
the value proposition is saving space on your local file

4
00:00:08,420 --> 00:00:11,930
servers while at the same time not interrupting access by

5
00:00:11,930 --> 00:00:14,070
your users and applications at all.

6
00:00:14,070 --> 00:00:18,740
What happens is that the AFS client on your registered server creates a heat map

7
00:00:18,740 --> 00:00:23,130
such that volatile hot files that are used regularly are cached locally on the

8
00:00:23,130 --> 00:00:26,050
file server and cool files are offloaded to Azure.

9
00:00:26,050 --> 00:00:29,430
Now you can customize the algorithm that AFS uses to

10
00:00:29,430 --> 00:00:32,010
determine what files to offload to Azure.

11
00:00:32,010 --> 00:00:33,170
I'll show you that in the demo.

12
00:00:33,170 --> 00:00:35,770
The offloaded files are not invisible.

13
00:00:35,770 --> 00:00:38,610
They will still show up in directory listings; however,

14
00:00:38,610 --> 00:00:41,230
they'll show up as consuming 0 bytes on disk.

15
00:00:41,230 --> 00:00:46,450
They're basically shortcuts or reparse points to the file as it exists in Azure.

16
00:00:46,450 --> 00:00:50,440
And on demand, AFS will recall the file from the cloud.

17
00:00:50,440 --> 00:00:54,780
You can gain additional space‑saving benefits on your local

18
00:00:54,780 --> 00:00:58,810
environment's file servers by combining cloud tiering with AFS

19
00:00:58,810 --> 00:01:02,400
with the data deduplication feature that's part of the Windows

20
00:01:02,400 --> 00:01:08,000
Server file services feature. We'll learn more about that later in the course.