none
An unexpected error occurred while the job was running. (ID 104 Details: Do not attach the filter to the volume at this time (0x801F000F)) RRS feed

  • Question

  • Hi,

    I run DPM 2012 R2 RU4 and want to protect some sql 2014 Databases from a stand-alone instance. The databases are located on a ReFS formatted drive. The system is running Server 2012 R2 on a genration 2 VM. The SQL Server runs in a different domain and is connected to DPM by using certificates.

    The backup is not succesfull and i get the following error:

    An unexpected error occurred while the job was running. (ID 104 Details: Do not attach the filter to the volume at this time (0x801F000F))

    vssadmin list writers shows no errors.

    Can somebody help me with this one?

    I Hope.

    Greetings.

    DJITS. 


    • Edited by DJITS Friday, November 7, 2014 12:03 PM Added Information
    Friday, November 7, 2014 12:00 PM

Answers

  • Hi,

    Microsoft System Center 2012 Data Protection Manager (DPM) Service Pack 1 (SP1) was the first version of DPM that supported protecting Windows Server 2012 workloads.

    A new file system called Recoverable File System (ReFs) was introduced in Windows Server 2012.  The Refs is a simplified subset of the NTFS file system and ReFs offers self healing capability to help with uptime by reducing / eliminating the need to run offline chkdsk against a volume.

    DPM 2012 SP1 / R2 can protect volumes formatted as ReFs but only as file data, not using DPM Application workload protection.  If you try to protect application data like SQL databases, SharePoint, Exchange DB or Hyper-V Virtual Machines (VM) that are hosted on an ReFs formatted volume, Initial replica creation and subsequent consistency check jobs will fail with the error 0x801F000F:

    Type: Consistency check
    Status: Failed
    Description: DPM is unable to continue protection for SQLServer\SQLDB\TestDb on SQLServer.Contoso.com because the change tracking information is corrupt (ID 30156 Details: Do not attach the filter to the volume at this time (0x801F000F))


    Type: Replica Creation
    Status: Failed
    Description:  DPM is unable to continue protection for \Backup Using Child Partition Snapshot\Appserver on vmhost because the change tracking information is corrupt (ID 30156 Details: Do not attach the filter to the volume at this time (0x801F000F))

    Cause
    This is currently by design - DPM 2012 SP1 / R2 does not support protecting application data hosted on Windows Server 2012 ReFs formatted volumes. Only file share / volume protection is allowed for ReFs formatted volumes.

    http://technet.microsoft.com/en-us/library/dn296605.aspx
    Support for protecting file server using Resilient File System (ReFS).

     

    Resolution
    The only real solution is to move the application data that you want DPM to protect to a NTFS formatted volume.

    Possible workaround - Use the Forcefixup key to revert to Consistency check work flow.

    Create the following registry key on the PS, restart DPMRA service and then try a CC once again.

    To Enable Force fix up for DPM agent

    A. On protected server, browse to the registry path: HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent\2.0.
    B. Create a DWORD registry value called "ForceFixup" and set it to 0x1.
    C. Restart the DPMRA service on protected server.

    NOTE - This will disable use of DPM filter so there will be some backup and possible server performance tradeoffs.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Saturday, November 8, 2014 5:55 PM
    Moderator

All replies

  • Hi,

    Microsoft System Center 2012 Data Protection Manager (DPM) Service Pack 1 (SP1) was the first version of DPM that supported protecting Windows Server 2012 workloads.

    A new file system called Recoverable File System (ReFs) was introduced in Windows Server 2012.  The Refs is a simplified subset of the NTFS file system and ReFs offers self healing capability to help with uptime by reducing / eliminating the need to run offline chkdsk against a volume.

    DPM 2012 SP1 / R2 can protect volumes formatted as ReFs but only as file data, not using DPM Application workload protection.  If you try to protect application data like SQL databases, SharePoint, Exchange DB or Hyper-V Virtual Machines (VM) that are hosted on an ReFs formatted volume, Initial replica creation and subsequent consistency check jobs will fail with the error 0x801F000F:

    Type: Consistency check
    Status: Failed
    Description: DPM is unable to continue protection for SQLServer\SQLDB\TestDb on SQLServer.Contoso.com because the change tracking information is corrupt (ID 30156 Details: Do not attach the filter to the volume at this time (0x801F000F))


    Type: Replica Creation
    Status: Failed
    Description:  DPM is unable to continue protection for \Backup Using Child Partition Snapshot\Appserver on vmhost because the change tracking information is corrupt (ID 30156 Details: Do not attach the filter to the volume at this time (0x801F000F))

    Cause
    This is currently by design - DPM 2012 SP1 / R2 does not support protecting application data hosted on Windows Server 2012 ReFs formatted volumes. Only file share / volume protection is allowed for ReFs formatted volumes.

    http://technet.microsoft.com/en-us/library/dn296605.aspx
    Support for protecting file server using Resilient File System (ReFS).

     

    Resolution
    The only real solution is to move the application data that you want DPM to protect to a NTFS formatted volume.

    Possible workaround - Use the Forcefixup key to revert to Consistency check work flow.

    Create the following registry key on the PS, restart DPMRA service and then try a CC once again.

    To Enable Force fix up for DPM agent

    A. On protected server, browse to the registry path: HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent\2.0.
    B. Create a DWORD registry value called "ForceFixup" and set it to 0x1.
    C. Restart the DPMRA service on protected server.

    NOTE - This will disable use of DPM filter so there will be some backup and possible server performance tradeoffs.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Saturday, November 8, 2014 5:55 PM
    Moderator
  • Hi Mike,Thanx for the quick response and your help.

    I tried the workaround and this works. It's only a development server so performance is not that important.

    Will ReFS be supported for other workloads in the near Future?

    Greetings,

    DJITS

    Monday, November 10, 2014 7:44 AM
  • Hi,

    I don't know if it's on the roadmap currently, but I can check and make sure it gets added if not. 


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, November 10, 2014 5:13 PM
    Moderator
  • And now I use DPM 2016, but I still need this workaround to backup Exchange on ReFS...

    Even if the technet page does not mention it !

    Thursday, February 16, 2017 4:41 PM