Microsoft released a new type of local file system in Windows Server 2012, it is called Resilient File System (ReFS). Microsoft designed this new file system because they see that there is a growth in storage (big data) and it works well with their new Storage Spaces feature in Windows Server 2012.
Initially it will be used for the file servers to prevent data loss and downtime.
In Windows Server 2012 you can choose between FAT32, NTFS and ReFS.
ReFS support features that contain functionality that proactively scans and repairs bad disk clusters (they use a “scrubber”). It’s a “Self-healing” file system and designed to prioritize the availability of data. If data corruption occurs the data will stay available without volume down-time. If data is corrupted an auto-repair (salvage) is triggered (it’s resilient to curruption) and it can remove the corrupted data, the volume will then be brought back online in a split second without the corrupted data.
1 yottabyte (YB) is 1.000.000.000.000.000.000.000.000 bytes (10^24), it goes from
- kB (kilobyte),
- MB (MegaByte),
- GB (Gigabyte),
- TB (Terrabyte),
- PB (PetaByte),
- EB (ExaByte),
- ZB (ZettaByte) to
- YB (YottaByte)
So, 1 Yottabyte should be enough room to store al tour files!
Advantages of ReFS
- Longer File Names and Paths, ReFS supports File Names and Paths up to 32.768 characters (NTFS up to 255 characters).
- Large volumes, ReFS supports volume sizes of 1 Yottabyte (NTFS up to 16 Exabytes).
- More capacity, ReFS supports file sizes up to 2^64-1 bytes.
- No data loss, Meta data is stored on another part of the disk.
- No Volume downtime, thanks to “salvage”.
- Backward Compatible, ReFS supports a subset of NTFS features plus Win32 APIs that are widely adopted.
Not supported in ReFS
- convert from NTFS to ReFS
- 8.3 naming convention (short names)
- Data deduplication
- Boot from ReFS (boot volume)
- Removable media or drives
- File-Based Compression
- Disk Quotas
- Object Identifiers
- Encrypted File System
- Named Streams
- Extended Attributes