File system NTFS ou REFS for Storage and Caching server


I'm working on the design of our new Projectwise Connect infrastructure (Last release)

I have 50 TB+ of Data expected on the storage server, 500 Gb/ 1 Tb on caching servers

Does anyone try to work with a volume formatted in Windows 2016 Resilient File System?   (REFS)   for storage and/or caching servers?

or do you have recommendations about that  ( Bentley or on your own)?   NTFS is not really resilient for XX Tb of data on a single server.

thanks for your advices.

Best regards

  • If you have the capability and it makes sense, there is no reason not to utilize REFS. Some refresher points:

    • Integrity streams: ReFS uses checksums to check for file corruption.
    • Automatic repair: When ReFS detects problems in a file, it will automatically enact corrective action.
    • Performance improvements: In a few particular conditions, ReFS provides performance benefits over NTFS.
    • Very large volume and file support: ReFS’s upper limits exceed NTFS’s without incurring the same performance hits.
    • Mirror-accelerated parity: Mirror-accelerated parity uses a lot of raw storage space, but it’s very fast and very resilient.
    • Integration with Storage Spaces: Many of ReFS’s features only work to their fullest in conjunction with Storage Spaces.
    • ReFS wins: Really large storage locations and really large VHDXs
    • ReFS wins: Environments with excessively high incidences of created, checkpointed, or merged VHDXs
    • ReFS wins: Storage Space and Storage Spaces Direct deployments
    • NTFS wins: Single-volume deployments
    • NTFS wins (potentially): Mixed-purpose deployments