I am speaking specifically about Article ID: 973455 - Last Review: September 25, 2011 - Revision: 4.0 Windows backup or restore errors 0x80070001, 0x81000037, or 0x80070003. I dont understand what a reparse point is. I don't understand what it is I'm to do with the information I get after typing <DIR /al /s> at the command prompt. I see a lot of information but uncertain how to address it in order to sucessfully complete a backup. Please explain what I am to do with the info I get after I type the command <DIR /al /s> Thank you

Hi, http://msdn.microsoft.com/en-us/library/aa365503(VS.85).aspx contains all info you need on reparse points. reparse points are in fact some kind of shortcut/link that redirects a folder. The error you encounter is usually related to "reparse points" pointing to locations that can not be backed up for some reason (for example on fat32 volume). So the best advice would be to find out: a) wether you have fat32 formatted disks. If so, consider converrting them to ntfs (using convert command) or not backing these files up using Windows Backup. b) Check your "Libraries" for included folders that do no longer exist. dir /al /s gives you list of "junctions" on the current folder and subfolders. Junctions are a very common kind of reparse point. You can use the information to find the "links" (reparse points) that cause the issue.

dir /as /s results in hundreds of lines, as does systeminternals' junction -s. For example junction -s returned \\?\C:\\Users\TheLoneLiberal.EVOLSWSYS\Documents\My Videos: JUNCTION Print Name : C:\Users\TheLoneLiberal.EVOLSWSYS\Videos Substitute Name: C:\Users\TheLoneLiberal.EVOLSWSYS\Videos How can I tell a valid junction from an invalid one?- Michael Faklis

The solution has nothing to do with reparse points or junctions. I found a posting on another site suggesting the problem was that the backup drive needed to be indexed. I indexed the backup disk and the backup worked just fine.- Michael Faklis

Except my backup drive is indexed and I am getting this error every week. As a non tech person, it seems to me, a bit of a joke that Microsoft hasn't found a proper answer to this problem and patched it. How are average users supposed to be able to follow all this tech stuff.