I purchased a new NAS device and I've created a FileHistory share on it for my File History backups.
All works well until the device goes offline for some reason: I have to restart it, a power bump, etc. After that, Windows forgets where my File History drive (destination) is and prompts me to reselect. A short list of previous backups is displayed and I'm required to pick an item from the list before the OK button becomes enabled.
The trouble is that these previous backups are always all from a different profile on the same computer. You see, I keep two profiles for myself: Work and Home. When File History is working properly it keeps everything separate under its appropriate folder on the share (
\\Device\Share\Home). All is right with the world; the birds are singing, the sun is shining and water is babbling in the brook.
Enter a device offline event.
Everything gets mixed up somehow and File History running under Work prompts me to reselect a destination, thinking (incorrectly) that its most recent backups are the ones that it finds under
\\Device\Share\Home. When I select one of those, backup proceeds normally except that my Work files are then stored under the share's Home folder.
Myself being one who prefers to not have my peas and carrots touch on my plate, I'd like to avoid this scenario. I don't mind having to reselect as that action is trivial—although I do believe that FH should be smart enough to survive one of these events—but it does trouble me that my files are going to the wrong place. My only option (so far) has been to rename the old folders and start completely new File History backups for each profile.
How can I prevent this happening and, moreover, fix it after it does happen?
- Why doesn't FH survive a device offline event, and instead prompts for a new destination upon reconnection?
- Why is FH running under Work incorrectly identifying backups under
\\Device\Share\Homeas its most recent sessions?
- How can we prevent #2 from happening?
- How can we fix #2 if/when it does happen?