It appears that the FH default catalog does not include <username>\AppData - I cannot imagine why, as its contents are obviously needed. My difficulties, mainly in understanding I think, started after adding AppData to the catalog:

  1. I received a batch of Event Log Warnings (ID 106) regarding directories not backed up due to reparse points. An actual example of one Event Properties window reads in part:

    "Directory was not backed up because it is a reparse point:"
    "If you want it to be protected, remove the reparse point."

    The wording of this is ambiguous. I think the first line is trying to say that the last element in the pathname (Content.IE5) is a reparse point, not a directory, and FH does not back up reparse points. Is that correct?

    In the third line, "If you want "it" to be protected...", what does "it" refer to, a directory not backed up or the reparse point? Contrary to the first line, they cannot both be the same thing. Also, what does "protected" mean? Neither a reparse point nor a directory will be protected from anything if it is removed either from the above pathname on the hard drive (as if you would!) or from the FH catalog. Removal from the catalogue would put a stop to the Warning Event though, I guess.
  2. I have seen posts in other forums in which people were confused by the above message and often asked how to remove the reparse point, but I have never seen a very helpful response: most launch into an explanation of what a reparse point is, rather than how to protect it.
  3. In this computer I have verified, by using dir /AL /S, that all users' reparse point destinations remain within the users' directory structure, so the existing redirected data should be backed up by FH, which is what would be expected, and which I hope holds true in general. (In the above example, the Content.IE5 reparse point redirects to \IE, a subdirectory of \INetCache which also contains the reparse point.)
  4. My problem is how to ensure reparse points can be restored if they are damaged by a disk crash, etc. I understand, but have not yet verified, that Windows (7) Backup also does not backup reparse points, but I have established that Windows System Image does. However, that seems like using a sledge hammer to drive a tack.
  5. Only recently I have come across Mklink which I believe to be a Windows program for creating reparse points. I am thinking of setting up a scheduled task to run regularly in order to keep a current record of reparse point definitions. Starting in the C:\Users folder, I would just run the script:
    dir C:\Users /AL /S > K:Junction.txt where K: is my external backup drive. Effectively this would give me a backup of reparse point definitions, and then I could use Mklink to recreate them if ever needed.
  6. Before I proceed any further I would welcome input from anyone who knows a better way of doing this, or would like to set me straight on my understanding of File History and reparse points. Many thanks.