1
00:00:00,740 --> 00:00:03,440
Configure Windows Server Storage.

2
00:00:03,440 --> 00:00:06,810
Let's start by running a high‑level comparison between the New

3
00:00:06,810 --> 00:00:13,860
Technology File System, NTFS, and the Resilient File System, ReFS. On

4
00:00:13,860 --> 00:00:16,660
the NTFS side, we have a very mature file system that's been around

5
00:00:16,660 --> 00:00:19,720
pretty much as long as I've been in the industry, if not longer,

6
00:00:19,720 --> 00:00:24,450
actually. Windows NT is when I came into the game. We can format

7
00:00:24,450 --> 00:00:28,970
volumes both for the OS drive, as well as fixed data disks, as well as

8
00:00:28,970 --> 00:00:30,390
removable data disks.

9
00:00:30,390 --> 00:00:32,500
It's a pretty universal file system.

10
00:00:32,500 --> 00:00:35,670
As we've seen elsewhere in this course, we can do quotas,

11
00:00:35,670 --> 00:00:38,790
compression, encryption. And that encryption can be whole

12
00:00:38,790 --> 00:00:41,870
volume encryption with BitLocker Drive Encryption, or it

13
00:00:41,870 --> 00:00:44,710
could be Encrypting File System, EFS.

14
00:00:44,710 --> 00:00:48,190
NTFS is known for its reliability and bad sector

15
00:00:48,190 --> 00:00:50,310
detection and bad sector repair.

16
00:00:50,310 --> 00:00:52,820
Well, you might wonder, well, if NTFS is so great,

17
00:00:52,820 --> 00:00:55,360
why did Microsoft design ReFS?

18
00:00:55,360 --> 00:00:58,890
Well, it came about much later in Windows Server 2012.

19
00:00:58,890 --> 00:01:02,050
I don't want to get into the whole history on it, it's got quite

20
00:01:02,050 --> 00:01:04,140
an interesting history as a matter of fact,

21
00:01:04,140 --> 00:01:08,610
but it's meant to extend NTFS particularly for data

22
00:01:08,610 --> 00:01:10,570
and virtual machine workloads.

23
00:01:10,570 --> 00:01:14,570
We can use ReFS only on fixed data disks.

24
00:01:14,570 --> 00:01:20,190
We can use BitLocker Drive Encryption, but not EFS. No removable data disks.

25
00:01:20,190 --> 00:01:25,730
The resiliency part of ReFS deals with detecting and fixing corruptions.

26
00:01:25,730 --> 00:01:29,940
It's an extension of the capability offered by NTFS.

27
00:01:29,940 --> 00:01:34,450
So we've got enhanced resiliency and failure detection and repair.

28
00:01:34,450 --> 00:01:37,090
We also have enhanced performance,

29
00:01:37,090 --> 00:01:40,540
especially with virtual machine workloads and when you're using

30
00:01:40,540 --> 00:01:44,080
Storage Spaces and Storage Spaces Direct.

31
00:01:44,080 --> 00:01:46,590
And then lastly, we have scalability.

32
00:01:46,590 --> 00:01:49,170
We've seen this in technology since the beginning.

33
00:01:49,170 --> 00:01:51,900
When there's a v2 of some technology,

34
00:01:51,900 --> 00:01:56,170
almost always the limits will be much greatly expanded.

35
00:01:56,170 --> 00:02:00,560
And so Microsoft says you can scale your ReFS volumes to millions of

36
00:02:00,560 --> 00:02:05,020
terabytes. If you want to know numbers and maximum volume sizes,

37
00:02:05,020 --> 00:02:08,060
that's basically trivia, we don't need to know that for the exam,

38
00:02:08,060 --> 00:02:11,500
but you can check the exercise files, and I'll point you to some

39
00:02:11,500 --> 00:02:13,900
online comparisons. At the end of the day,

40
00:02:13,900 --> 00:02:16,700
I just want to make sure you know about some of the top

41
00:02:16,700 --> 00:02:19,840
line differences between NTFS and ReFS.

42
00:02:19,840 --> 00:02:24,880
A big one with ReFS to repeat is that we cannot boot from an ReFS volume

43
00:02:24,880 --> 00:02:33,000
and that it shines particularly well when you're doing Storage Spaces and S2D in Windows server failover clusters.