File History vs VSS vs 3rd party backup app for open workstation files

1. Does Windows 10 File History back up open files, eg. open excel or pdf's or only closed files?
I use a document management app that stores docs in Sql but temporarily copies them to a user\appdata\roaming\ subfolder while the user is working on the file. Then the app is supposed to copy the saved word, excel, or pdf back toSql when user saves and closes the file. Many times the app fails to copy back to Sql and user has to manually do it. But sometimes the file has been deleted. Then you have to hope it's in the recycle bin, or try a third party undelete tool and wait for that to finish searching.

2. would setting VSS to auto start be a better solution, or does it only store closed files?


3. What is the interaction of File History and VSS on Win 10 workstation? Does FH take over from VSS? I enabled both FH and VSS on a workstation, started VSS service. But I don't see the configuration choices for VSS.

4. I might just have to find a low impact 3rd party continuous backup app for workstations, that could backup to my second hd or to my nas. Any suggestions? (I'd have used Crashplan but i think it won't do local backups in latest ver.)

Len Raphael
Oakland CA

Windows file history isn't really a viable backup solution. It works under the severe constraints of of being a totally automated system that must be usable with only a single drive, which is all many computers have. For most people (who never think of making backups until it is too late) it is the closes thing to a backup they will ever have.

But as a backup it leaves much to be desired. In particular if the drive fails you will loose everything. By all means maintain your own backups in a way appropriate for your situation. Windows file history can be useful but never rely on it. Maintain your own backups with the assumption it isn't there. If it works for you consider it a bonus.

LMiller7 said:

Windows file history isn't really a viable backup solution. It works under the severe constraints of of being a totally automated system that must be usable with only a single drive, which is all many computers have. For most people (who never think of making backups until it is too late) it is the closes thing to a backup they will ever have.

But as a backup it leaves much to be desired. In particular if the drive fails you will loose everything. By all means maintain your own backups in a way appropriate for your situation. Windows file history can be useful but never rely on it. Maintain your own backups with the assumption it isn't there. If it works for you consider it a bonus.

That isn't true. I have file history backup set up so that it backs up data files to an SD card permanently inserted in the computer's SD card slot. On my mother-in-law's business computer I use file history backup to the SD card to keep her data files backed up daily. About once per month I do a complete system image backup using Macrium Reflect. In the event of SSD failure the plan would be to restore the last system image backup (stored on a NAS), then update the data files from the SD card which, hopefully, would be less than 24 hours old.