I have found plenty of articles online warning of risk of data loss or corruption for drives with write-buffer enabled in the event of power loss. However, I haven't found any that actually refer to the scale of the risk.
I'm looking to build a mirrored file server in Storage Spaces on Windows Server 2016 for the purposes of a small video-editing office. Performance is very important (hence the write-buffer consideration), and our server would handle mostly two types of important writes: Uploading footage, and saving a project or document file.
This leads me to wonder what the worst case scenario would be in the event of unexpected power loss.
For uploading footage, I would expect any interruption to the server to cause a visible network failure to any file transfer in progress. Therefore, unless the power failure occurred seconds after the network portion of the file transfer completed, they would be aware of the need to restart the file transfer once the server was back online. Since I would be aware of the server going down, I could advise the office to use a sync program to presumably overwrite any corrupted files with the local master copies.
As for saving documents and project files, most of them should be so tiny as to have minimal risk of even being in the buffer at the time of failure. And if that wasn't the case, having autosaves or an open version still on the user's computer would give them a second chance. The only risk I can really see is if the power failure occurred right as they saved and closed the file, and that program didn't store rolling autosaves.
Is my assessment accurate, or have I overlooked something? Can corruption in this situation affect more data than that which was being written?
Edit: I should stress that I'm not particularly looking for conclusions about what I should do in this scenario. I merely want to properly understand the possibilities so I can make an informed decision on the reality of this risk.
The many web pages I've read on the issue so far have been frustratingly ambiguous, particularly in regards to differentiating between 'write caching' and 'write-cache buffer flushing'.