none
UNable to Protect Hyper V Core Server RRS feed

  • Question

  • Hi, I am trying to protect using DPM2010  my 2 physical Hyper –V Host wich is shareing a SAn Storage. Once I try to creat a protection group and expand Hyper v Hosts I receive the below 2 message.

     

    Host 01

    DPM is unable to enumerate C:\on Computer Server (ID 3055)

     

    Host 02

    DPM is unable to enumerate contents in

    \\?\Volume{9db0a6be-327e-11df-a4f3-806e6f6e6963}\ on the protected computer

    Server Name. Recycle Bin, System Volume Information folder,

    non-NTFS volumes, DFS links, CDs, Quorum Disk (for cluster) and other

    removable media cannot be protected. (ID: 38)

     

    C:\Program Files\Microsoft Data Protection Manager\DPM\Datasource\PSDatasourceConfig.xml

    D:\WindowsImageBackup\*.  D drive is Active.

    Both the Hyper V server run on Windows Server 2008r Core.

    Dpm Agent is running

    Friday, August 12, 2011 4:35 AM

Answers

  • This error happens because the Windows NTFS file system \$Extend\$Reparse metafile on the server specified in the error has corruption that needs to be fixed. 

     

    To fix the NTFS file system, run chkdsk /f against the problematic volume then reboot.      The chkdsk output should show that we fixed index entries in $R of file 26.

     

    <snip>

    Log Name:      Application

    Source:        Microsoft-Windows-Wininit

    Event ID:      1001

    Task Category: None

    Level:         Information

    Keywords:      Classic

    User:          N/A

    Computer:      PS_Server_name

    Description:

     

    Checking file system on C:

    The type of the file system is NTFS.

     

    One of your disks needs to be checked for consistency. You

    may cancel the disk check, but it is strongly recommended

    that you continue.

     

    Windows will now check the disk.                        

     

    CHKDSK is verifying files (stage 1 of 3)...

     

     132352 file records processed.                                        

     File verification completed.

      199 large file records processed.                                  

      0 bad file records processed.                                    

      0 EA records processed.                                           

      348 reparse records processed.                                     

     

    CHKDSK is verifying indexes (stage 2 of 3)...

    The reparse point index entry in file 0x1a points to file 0x131

    but the file has no reparse point in it.

    Deleting an index entry from index $R of file 26.

    The reparse point index entry in file 0x1a points to file 0x132

    but the file has no reparse point in it.

    Deleting an index entry from index $R of file 26.

    The reparse point index entry in file 0x1a points to file 0x13

    Monday, August 15, 2011 6:24 PM
    Moderator