none
DPM 2019 insists offering non-existing VM a for Hyper-V host RRS feed

  • Question

  • Hello everybody,

    a fresh install of DPM 2019 on Windows Server 2019 Datacenter shows all VMs on a freshly installed Windows Server 2019 Datacenter Hyper-V host, and it backs them up just fine. However, DPM offers a strange VM named "Th-VM" which does not exist, which we did never create, and whose name would be far away from our VM naming standards. So if we choose Hyper-V auto-protection for that host, DPM tries to backup that VM and, of course, fails doing so. We can run backups fine if we uncheck both Auto-Protection and that strange VM. A refresh of the host in the DPM protection group wizard (having the host not expanded in the tree) still shows up this "Th-VM" VM.

    Why does DPM offer us a VM which does not and did never exist, and how can we get rid of it? Thanks!


    Best Regards, Stefan Falk

    Wednesday, April 17, 2019 5:29 PM

All replies

  • Hi Stefan,

    I have not heard nor encountered this issue, it does seem very strange, it could possibly be a bug.

    Could you provide a screenshot of this interesting behavior?

    Have you also checked the DPM logs for any more details perhaps?


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, April 17, 2019 6:16 PM
  • Hello Leon,

    Thank you very much for your super-fast response! Here is the screen shot:

    DPM screen shot

    Also please not that strange backslash in "RCT\Th-VM\".

    Indeed we have strange warnings and errors in the application event log, but I have no idea whether they are relevant for this issue - see https://1drv.ms/u/s!AnuxuhxP0zblr710SfxaXrbbTdUZIQ

    Shall I check some other kind of log?


    Best Regards, Stefan Falk

    Wednesday, April 17, 2019 7:15 PM
  • Thanks, have a look at the following logs:

    DPM server log:

    • C:\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPMCurr.errlog

    Hyper-V hosts logs:

    • C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\DPMRACurr.errlog

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, April 17, 2019 7:25 PM
  • Hello Leon,

    I gathered:

    PS C:\> Get-ChildItem '\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp' -File | Select-String 'Th-VM' | Export-Csv "$env:USERPROFILE\Documents\DPM-Server-Log.csv" -NoClobber -NoTypeInformation -Encoding UTF8
    PS C:\> Get-ChildItem '\\sf-hv2019\c$\Program Files\Microsoft Data Protection Manager\DPM\Temp' -File | Select-String 'Th-VM' | Export-Csv "$env:USERPROFILE\Documents\DPM-Agent-Log.csv" -NoClobber -NoTypeInformation -Encoding UTF8

    You can find the results in https://1drv.ms/u/s!AnuxuhxP0zblr711n7nuhvjDyTtypg

    Thanks for looking into that!


    Best Regards, Stefan Falk

    Thursday, April 18, 2019 8:26 AM
  • I found some interesting things, here's one of them:

    DatasourceId=[0193bc01-fc55-41f8-b0e5-829b3b4563ad], DatasourceName=[RCT\Th-VM\]","DPMAccessManager2.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\DPMAccessManager2.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"

    Then we get warnings of the following:

    TaskExecutor.cs(332)		79AF4716-190E-4D86-AB4C-5557ED3EB259	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\CT-ETT-MAIL03"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13156","1538	1084	04/13	16:33:05.075	01	TaskExecutor.cs(332)		11AB6C0A-D3FC-4C92-B81D-8F08119E0521	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\SF-SQL2019"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13198","1538	1084	04/13	16:33:05.263	01	TaskExecutor.cs(332)		235BF3EB-BA11-4379-8867-2DA8EC88A71B	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\SF-MAIL2019"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13219","1538	1084	04/13	16:33:05.325	01	TaskExecutor.cs(332)		84501C9D-9878-4472-8E5B-C8B89F46EEB4	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\SF-CA2019"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13240","1538	1084	04/13	16:33:05.404	01	TaskExecutor.cs(332)		25F45DA7-1EFC-416C-9A6D-41393FDD21C7	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\CT-ETT-WEB02"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13269","1538	1084	04/13	16:33:05.513	01	TaskExecutor.cs(332)		93D329FF-92B9-44EE-BC5B-EABBA8722194	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\SF-FILE2019"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13290","1538	1084	04/13	16:33:05.594	01	TaskExecutor.cs(332)		A3BD5261-117C-4D22-86BA-7C0EED3C0D0C	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\SF-ADMIN2019"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13311","1538	1084	04/13	16:33:05.672	01	TaskExecutor.cs(332)		F90EA7B7-E460-4B6D-9477-C526573A31DD	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\CT-ETT-SQL01"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13332","1538	1084	04/13	16:33:05.736	01	TaskExecutor.cs(332)		056861CA-24E3-47C3-8ADE-C811DAFEB914	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\SF-INFRA2019"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"
    "True","13353","1538	1084	04/13	16:33:05.892	01	TaskExecutor.cs(332)		7C49A92A-F9CA-4A68-BD3E-C2114EE872FA	WARNING	  <q1:Parameter Name=""datasourcename"" Value=""Th-VM\CT-ETT-TFS02"" />","MSDPM103.errlog","\\sf-dpm2019\c$\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPM103.errlog","Th-VM",,"System.Text.RegularExpressions.Match[]"

    It looks like DPM thinks that the "Th-VM" is the host or the datasource for some reason, as you can see in the first log message I posted above "DatasourceName=[RCT\Th-VM\]"

    Could you check the DPMAccessManager2.errlog and the MSDPM103.errlog logs?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, April 18, 2019 8:39 AM
  • Hello Leon,

    sure! You are really super-fast. Please see https://1drv.ms/u/s!AnuxuhxP0zblr712S7EztHUKO2ZTwA


    Best Regards, Stefan Falk

    Thursday, April 18, 2019 8:52 AM
  • It's difficult to say, it would be easier to compare it with another DPM version that is backing up Hyper-V to see the difference in the datasource.

    It does look like a bug though.

    Are there any virtual machines with older configuration version?

    Or any virtual machine that has been imported/exported?


    You could try reinstalling the DPM agents on the Hyper-V hosts, but this would disrupt the backups, unless you have a free time window to do this.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, April 23, 2019 6:48 AM
  • Hello Leon,

    Thanks for your valuable efforts! About half of the machines were live-migrated from a Windows Server 2016 Hyper-V host, the other half was freslhy created on the new one. All VMs are of configuration version 9.0 on the new host.

    If needed, I could remove the VMs from protection, uninstall and reinstall the agent on the host and backup them freshly. Shall I try, really?


    Best Regards, Stefan Falk

    Tuesday, April 23, 2019 7:44 PM
  • If you have the possibility to remove the VMs from the protection group, reinstall the DPM agents, I would suggest you to try, this way we have at least tried to solve the strange issue you're having.

    If this doesn't help, it might indeed be a bug in DPM 2019, then it might be worth raising a ticket about this directly to Microsoft.

    Also note the following that is stated on the DPM 2019 release notes (even though if this doesn't concern you, it might be good information):

    Hyper-V VMs are protected twice on VM upgrade

    Description: When upgrading a Hyper-V VM from Windows Server 2012 R2 to Windows Server 2016, two versions of the VM appear in the Create Protection Group wizard.

    Workaround: For the protected VMs which are about to be upgraded, make sure to stop protection with retain data before upgrading the VM. Then, upgrade the VM and reprotect it in a new protection group. While configuring reprotection, do a refresh on the VM host for DPM to detect the VM upgrade and protect it as RCT VM.

    Reference:
    https://docs.microsoft.com/en-us/system-center/dpm/dpm-release-notes?view=sc-dpm-2019#hyper-v-vms-are-protected-twice-on-vm-upgrade


    Blog: https://thesystemcenterblog.com LinkedIn:



    • Edited by Leon Laude Tuesday, April 23, 2019 9:24 PM
    Tuesday, April 23, 2019 9:20 PM
  • Hello Stefan,

    Just wanted to check if you have any update on your issue?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, April 26, 2019 6:55 AM
  • Hello Leon,

    I'll try reinstalling the agent tomorrow (when nobody but me is working ;-) and will report here. Thanks again!


    Best Regards, Stefan Falk

    Friday, April 26, 2019 7:47 AM
  • Thanks for the update Stefan.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, April 26, 2019 8:02 AM
  • Hello Leon,

    I did the following:

    1. Remove the complete Hyper-V protection group in DPM including removing the disk replicas (but keeping the tape records).
    2. Uninstall DPM-Agent from the Hyper-V-Host using Uninstall-Package.
    3. Removed the host from the DPM protection agent. Besides the tape recovery points of  the VMs, DPM should now not know anything about the host any more.
    4. Rebooted the host.
    5. Reinstalled the DPM agent.
    6. Connected the agent in DPM.
    7. Created a new protection group - DPM still offers that strange VM named "Th-VM".

    So the procedure did not help. Where on earth does DPM get that VM name from?


    Best Regards, Stefan Falk

    Saturday, April 27, 2019 8:39 AM
  • Thanks for sharing and trying this Stefan, in this case I would suggest you create a case to Microsoft about this.

    As it appears to be some bug that we cannot fix.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, April 27, 2019 8:43 AM
  • Thank you very much for your engagement and your super-fast responses, Leon! I will open a case and report here the results (but it may take some time, I guess ;-)


    Best Regards, Stefan Falk

    Saturday, April 27, 2019 8:46 AM
  • Hello again,

    surprisingly, on a totally fresh install of DPM 2019 on a new Windows Server 2019 box with the Hyper-V role also installed, DPM offers that funny "RCT\Th-VM" VM also! This is at a customer's site, totally independent from the one mentioned above. And it is on a plain new fresh installation. Shouldn't someone else have seen this also?


    Best Regards, Stefan Falk

    Saturday, July 13, 2019 11:31 AM
  • DPM 2019 and Windows Server 2019 are kind of new and i doubt many people have put this combinaton into production. Especially since DPM2019 doesn't support a lot of "older" workloads like Sharepoint and Exchange 2010/2013.

    Thursday, July 18, 2019 4:26 PM
  • Hello Leon!

    Is there any news from Microsoft? I have the same issue but on DPM 2016 1807 (on 2012 R2) and with server 2019 with Hyper-V with all updates.

    Also DPM could not see any VM genration 2.0 until update them to version 9.0, and there is no problem with generation 1 VMs.

    Monday, September 23, 2019 9:17 PM