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

Posted: January 29, 2016 in Data Protection Manager

This one is an old draft that i forgot to Post…

Application: System Center 2012 R2: Data Protection Manager

Protected Server: Windows Server 2012 R2

Protected Server Roles: Hyper-V

Protected Server File System for VM’s: ReFS (Resilient File System)

I created a Protection Group for Hyper-V, and while replication… WHAM!, critical Alert, Replica Inconsistent.

I check under Monitoring

dpm-alerts

Affected area:   \Online\HYPERV-VM

Occurred Since:  01/29/2015 11:22:47 AM

Description:

The replica of Microsoft Hyper-V \Online\HYPERV-VM on HYPERVSERVER.TEST.LOCAL is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

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

********************************************************************

In this particular case the error is related to the File System type of the Protected Server (ReFS). DPM does not support to ReFS File System (at least at the time when i wrote the post).

What you need to do:

There is a quick fix, so roll up sleeves… Registry…

Open the Registry

  1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0
  2. Create a DWORD (32 bit value)
  3. Name it “ForceFixup” (don’t forget to remove the quotation marks)
  4. Value data will be 1
  5. Base will be Hexadecimal
Close the registry, then go to Power Shell and execute:
  1. net stop dpmra (if you receive “The DPMRA service is not started”, execute the net start…)
  2. net start dpmra
close Power Shell, Open DPM Management Console and re-run the replicacion Job.
YOU ARE DONE, CONGRATULATIONS!

 

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s