Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
backup error 0x81000037

Answered backup error 0x81000037

  • Saturday, November 05, 2011 3:48 AM
     
     
    Sign In to Vote
    0

    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

     

All Replies

  • Sunday, November 06, 2011 10:08 AM
     
     Answered
    Sign In to Vote
    0

    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.


     
  • Wednesday, February 15, 2012 9:12 PM
     
     
    Sign In to Vote
    0

    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

     
  • Sunday, February 19, 2012 6:00 PM
     
     Proposed Answer
    Sign In to Vote
    0
    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

    • Proposed As Answer by Michael Faklis Sunday, February 19, 2012 6:00 PM
    •  
     
  • Saturday, May 12, 2012 9:52 PM
     
     Proposed Answer
    Sign In to Vote
    0

    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.

    • Proposed As Answer by erohed Wednesday, August 29, 2012 4:15 PM
    •  
     
  • Sunday, November 18, 2012 1:53 PM
     
     Proposed Answer Has Code
    Sign In to Vote
    0

    I realize this thread is a little old but I've just had to solve the same issue for myself (Error 0x81000037). This thread is still top of search results, right after the Article ID you quoted. It appears not to have to do with juntions/reparse points at all. This is what I found to be the most relevant info:

    To quickly check if my suggested solution even applies, open a command prompt (as administrator) and type the following, where X: is your backup destination drive:

    Fsutil fsinfo ntfsinfo x:
    If the "Bytes Per Physical Sector" shows 4096 or (Not Supported), read on:

    KB2510009: Microsoft support policy for 4K sector hard drives in Windows

    The relevant outtake is that Windows Backup cannot properly access a disk formatted with 4K native sectors. Windows 7 and Windows Server 2008 R2 or older versions only have support for 512K sectors, which can be emulated on an Advanced Format disk. Reformatting my external backup disk using a tool supplied by the manufacturer has allowed it to report as using 512K sectors (note fsutil might still show (Not Supported) on the Bytes Per Physical Sector field, which is expected). Upgrading to Windows 8 or Server 2012 is also a valid solution, but doing so without a backup would be a judgement call.

    Here is the thread that I found this info in eventually:
    TechNet: Backup Fails With Error Code "2155348010"

    • Proposed As Answer by Agent377 Sunday, November 18, 2012 1:54 PM
    •