Protection Group with Hyper-V VMs fails with Error ID 53 Details: Not implemented (0x80000001)

Hi,

have DPM 2012 R2 with Rollup 6 in Domain (as Hyper-V VM Gen 2). SQL Server 2012 SP2 on DPM Server. On Hyper-V Host newest Agent. All instalations/updates without any issue. As Storage Pool have a vhdx an a SATA Disk bounded via Hyper-V Settings.

When i create a Protection Group with Folders/SQL Database works fine like it should.

When i create a Protection Group to Backup a Hyper-V on Host got at once after created Error:

"DPM failed to communicate with dpmserver.domain because of a communication error with the protection agent. (ID 53 Details: Not implemented (0x80000001))"

Windows Firewall on Host and DPM Server are both off. No other Error/Warning in Windows Event Viewer. 

Have no idea, need your help.

Regards

Martin

 


  • Edited by l054432 Saturday, May 30, 2015 2:29 PM
May 30th, 2015 2:29pm

Hi,

yes more times. Also tried second Hyper-V Host to protect the VMs there, same problem.

Regards

Martin


  • Edited by l054432 Sunday, May 31, 2015 7:51 AM
Free Windows Admin Tool Kit Click here and download it now
May 31st, 2015 7:51am

Hi,

Are hosts domain memebers ?

If not, check user which used for DPM, status in DPM and host servers.



  • Edited by Gerardas Monday, June 01, 2015 10:10 AM
June 1st, 2015 10:09am

Hi,

ty for all the answers. Yes the Hyper-V Hosts are both Domain joined. Same Domain as DPM Server. I have no Hyper-V Cluster, only simple 2 Hyper-V Host which are included in DPM Server (both with Agents). Does the DPM Server Domain Account do need to be in Hyper-V Administratoren group?

Regards

Martin 


  • Edited by l054432 Monday, June 01, 2015 12:19 PM
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2015 12:19pm

Hi,

found the issue. My Hyper-V VMs where on an ReFS formated partition. Changed to NTFS and it worked perfectly.

Ty all for your help! Regards

Martin

  • Marked as answer by l054432 Tuesday, June 02, 2015 8:15 AM
June 2nd, 2015 8:15am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics