Azure Backup should be enhanced to allow the backup of ReFS file systems. I need a cost-effective platform that maximizes data availability, scales efficiently to very large data sets across diverse workloads, and guarantees data integrity by means of resiliency to corruption (regardless of software or hardware failures). ReFS is a new file system that targets these needs while providing a foundation for significant future innovations. The integrated storage stack comprising ReFS and the new Storage Spaces feature in Windows Server 2012 allows me to now deploy the most cost-effective platform for available and scalable data access using commodity storage.
In particular, the following significant functionality included with ReFS is important to us:
Integrity. ReFS stores data in a way that protects it from many of the common errors that can normally cause data loss. When ReFS is used in conjunction with a mirror space or a parity space, detected corruption—both metadata and user data, when integrity streams are enabled—can be automatically repaired using the alternate copy provided by Storage Spaces. In addition, there are Windows PowerShell cmdlets (Get-FileIntegrity and Set-FileIntegrity) that you can use to manage the integrity and disk scrubbing policies.
Availability. ReFS prioritizes the availability of data. Historically, file systems were often susceptible to data corruption that would require the system to be taken offline for repair. With ReFS, if corruption occurs, the repair process is both localized to the area of corruption and performed online, requiring no volume downtime. Although rare, if a volume does become corrupted or you choose not to use it with a mirror space or a parity space, ReFS implements salvage, a feature that removes the corrupt data from the namespace on a live volume and ensures that good data is not adversely affected by nonrepairable corrupt data. Because ReFS performs all repair operations online, it does not have an offline chkdsk command.
Scalability. As the amount and size of data that is stored on computers continues to rapidly increase, ReFS is designed to work well with extremely large data sets—petabytes and larger—without performance impact. ReFS is not only designed to support volume sizes of 2^64 bytes (allowed by Windows stack addresses), but ReFS is also designed to support even larger volume sizes of up to 2^78 bytes using 16 KB cluster sizes. This format also supports 2^64-1 byte file sizes, 2^64 files in a directory, and the same number of directories in a volume.
Proactive Error Correction. The integrity capabilities of ReFS are leveraged by a data integrity scanner, which is also known as a scrubber. The integrity scanner periodically scans the volume, identifying latent corruptions and proactively triggering a repair of that corrupt data.
This already under review, for updates follow this idea:
REFS support would be very welcome when using the agent in SC DPM as well. I would like to point the recovery folder to an existing REFS volume but at the moment, that's not possible. Thanks!
George Caba commented
Having support for ReFS formatted volumes is definitely a must and I believe support for it should be added sooner than later.