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

Answers

  • Hi Stefan,

    Thanks for that, I extracted the xml information that contains the bogus th-vm/ entry and it is the Hyper-V rct writer that is passing it to us.   It is strange that the diskshadow list writer did not list it however you will need to post a forum post in the Windows Hyper-V form or open a case with them. 


    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.


    Wednesday, December 18, 2019 4:30 PM
    Moderator

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
  • Hi,

    Just checking to see if you have any update on your issue?

    @Crash The Great: No news unfortunately.

    If your issue was resolved, may I ask you to mark all the answers that helped you? This way it will also help others in the future who face the same challenge. Many thanks in advance!


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, December 11, 2019 9:51 PM
  • Hello everybody,

    as far as I am concerned, the issue is not resolved up to now. Worse, I see it at *every* DPM 2019 site where a Hyper-V host, clustered or not, is backed up.


    Best Regards, Stefan Falk

    Wednesday, December 11, 2019 9:54 PM
  • Thanks for the information Stefan, this really sounds like a bug, if it affects your production I would definitely raise a ticket directly to Microsoft (if it's indeed a bug it will be free of charge).

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, December 11, 2019 11:50 PM
  • Hello,

    The list of virtual machines that available for protection are enumerated by the Hyper-V Vss Writer on the Hyper-V Server.  When you click on the "Refresh" button after highlighting the Hyper-V server DPM will clear the cached information and get a new list of available VM's to protect from the Hyper-V VSS Writer.

    You can try the below steps to see what the results are.

    test-1 - get the list of VM's from the Hyper-V Writer on the Hyper-V server.
    ====

    1) On the Hyper-V server, open an administrative command prompt and run the following.
       C:\>diskshadow.exe /l c:\temp\writers.txt  - that will start a diskshadow console and enable the log.

    2) Type: list writers

    DISKSHADOW> list writers

    3) After it lists the writer output, type exit to close the diskshadow console.

    DISKSHADOW> exit 

    4) Now run:  Find /i "Th-Vm" c:\temp\writers.txt

    5) Look to see if the Th-VM  is returned - if so it's a Hyper-V issue and you should open a ticket with the Windows Hyper-V team.

    Test-2 - stop the Hyper-V writer on the Hyper-V server, then do a refresh on DPM.
    =====
    1) On the Hyper-V Server, open computer management and under services stop the " Hyper-V Virtual Machine Management" service then change the startup type from Automatic to Disabled.

    2) On the DPM Server, modify the protection group that contains the Hyper-V VM protection.  Without clicking on the + sign next to the Hyper-V server just select / highlight it,  then click on the "Refresh" button to clear the cache and retrieve latest data.

    3) After it finished refreshing, expand out the Hyper-V server and the only VM's that should be listed are ones that are currently protected.  All other VM's including the Th-VM should not be listed.   If that is true then open a ticked with the Windows Hyper-V support.

    Please revert back with the results.

    Regards
    Mike Jacquet


    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.

    Thursday, December 12, 2019 12:12 AM
    Moderator
  • Hello Mike,

    Thank you for your suggestion! I will try and report here as soon as possible.


    Best Regards, Stefan Falk

    Thursday, December 12, 2019 8:53 AM
  • Hello Mike,

    I have performed your tests as follows:

    PS C:\> diskshadow.exe /l C:\Temp\writers.txt
    
    
    DISKSHADOW> list writers
    Verfassermetadaten werden aufgeführt...
    
    	* WRITER "Task Scheduler Writer"
    		- Verfasserkennung = {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
    		- Instanzkennung = {1bddd48e-5052-49db-9b07-b96f96727e6b}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = FALSE
    		- Ausgeschlossene Dateien:
    		+ Komponente "Task Scheduler Writer:\TasksStore"
    			- Name: TasksStore
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \TasksStore
    			- Beschriftung: Tasks Store
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: FALSE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- C:\Windows\System32\Tasks
    				- C:\Windows\Tasks
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    
    	* WRITER "VSS Metadata Store Writer"
    		- Verfasserkennung = {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
    		- Instanzkennung = {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = FALSE
    		- Ausgeschlossene Dateien:
    		+ Komponente "VSS Metadata Store Writer:\WriterMetadataStore"
    			- Name: WriterMetadataStore
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \WriterMetadataStore
    			- Beschriftung: VSS Express Writer Metadata Store
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- C:\Windows\Vss\Writers
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    
    	* WRITER "Performance Counters Writer"
    		- Verfasserkennung = {0bada1de-01a9-4625-8278-69e735f39dd2}
    		- Instanzkennung = {f0086dda-9efc-47c5-8eb6-a944c3d09381}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = FALSE
    		- Ausgeschlossene Dateien:
    		+ Komponente "Performance Counters Writer:\PerformanceCounters"
    			- Name: PerformanceCounters
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \PerformanceCounters
    			- Beschriftung: Performance Counters
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- C:\Windows\System32
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    
    	* WRITER "System Writer"
    		- Verfasserkennung = {e8132975-6f93-4464-a53e-1050253ae220}
    		- Instanzkennung = {06fb5dfd-11b8-467f-9223-68228aa28429}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = TRUE
    		- Ausgeschlossene Dateien:
    		+ Komponente "System Writer:\System Files"
    			- Name: System Files
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \System Files
    			- Beschriftung: System Files
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    ... (lots of file names listed)
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "System Writer:\Win32 Services Files"
    			- Name: Win32 Services Files
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \Win32 Services Files
    			- Beschriftung: Win32 Services Files
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- c:\program files (x86)\fujitsu\serverview suite\remote connector
    				- c:\program files\fujitsu\serverview suite\agents\onlinediagnostic\testmanager
    				- c:\program files\fujitsu\serverview suite\agents\server control
    				- c:\program files\fujitsu\serverview suite\raid manager
    				- c:\program files\microsoft data protection manager\dpm\bin
    				- c:\programdata\microsoft\windows defender\platform\4.18.1911.3-0
    				- c:\windows\system32
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    
    	* WRITER "Microsoft Hyper-V VSS Writer"
    		- Verfasserkennung = {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
    		- Instanzkennung = {7fb93137-6286-4f50-9ba8-c9951746b1bf}
    		- Unterstützt Wiederherstellungsereignisse = TRUE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_ALWAYS
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_IF_CAN_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = FALSE
    		- Ausgeschlossene Dateien:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\1AB09FC0-3C74-4112-B436-9A7D3F69F50C"
    			- Name: 1AB09FC0-3C74-4112-B436-9A7D3F69F50C
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \1AB09FC0-3C74-4112-B436-9A7D3F69F50C
    			- Beschriftung: Online\SF-CA2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\1D28B008-5712-4042-A74F-36EC15997934"
    			- Name: 1D28B008-5712-4042-A74F-36EC15997934
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \1D28B008-5712-4042-A74F-36EC15997934
    			- Beschriftung: Online\SF-DC2016
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\256DAEB7-35C4-4DCE-B963-2745FF99DD6C"
    			- Name: 256DAEB7-35C4-4DCE-B963-2745FF99DD6C
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \256DAEB7-35C4-4DCE-B963-2745FF99DD6C
    			- Beschriftung: Online\SF-INFRA2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\33528DD4-1575-499E-BEF4-8513B988D66A"
    			- Name: 33528DD4-1575-499E-BEF4-8513B988D66A
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \33528DD4-1575-499E-BEF4-8513B988D66A
    			- Beschriftung: Online\CT-ETT-TFS02
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\34ABC377-0161-40DF-BA74-A1D8BEBB3ED9"
    			- Name: 34ABC377-0161-40DF-BA74-A1D8BEBB3ED9
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \34ABC377-0161-40DF-BA74-A1D8BEBB3ED9
    			- Beschriftung: Online\SF-WSUS2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\389EA614-92D2-4CAC-8DC0-FB6BC9DE5C76"
    			- Name: 389EA614-92D2-4CAC-8DC0-FB6BC9DE5C76
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \389EA614-92D2-4CAC-8DC0-FB6BC9DE5C76
    			- Beschriftung: Online\SF-SQL2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\40A23698-BC00-43C7-A1BB-D207D3372C09"
    			- Name: 40A23698-BC00-43C7-A1BB-D207D3372C09
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \40A23698-BC00-43C7-A1BB-D207D3372C09
    			- Beschriftung: Online\SF-MAIL2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\545AD62F-151E-4E42-A215-39B9134B341F"
    			- Name: 545AD62F-151E-4E42-A215-39B9134B341F
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \545AD62F-151E-4E42-A215-39B9134B341F
    			- Beschriftung: Online\SF-SP2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\551AA35B-24E5-41CA-AB6F-41A99714B30B"
    			- Name: 551AA35B-24E5-41CA-AB6F-41A99714B30B
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \551AA35B-24E5-41CA-AB6F-41A99714B30B
    			- Beschriftung: Online\SF-ADMIN2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\56C96990-FA09-468B-A51F-B87744F88558"
    			- Name: 56C96990-FA09-468B-A51F-B87744F88558
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \56C96990-FA09-468B-A51F-B87744F88558
    			- Beschriftung: Online\CT-ETT-TFBLD04
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\8760C0C8-9095-4EC9-8B35-4CF21D459D4D"
    			- Name: 8760C0C8-9095-4EC9-8B35-4CF21D459D4D
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \8760C0C8-9095-4EC9-8B35-4CF21D459D4D
    			- Beschriftung: Online\SF-SERVICE2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\8E8E8A67-A336-43C8-89E5-3C086376B755"
    			- Name: 8E8E8A67-A336-43C8-89E5-3C086376B755
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \8E8E8A67-A336-43C8-89E5-3C086376B755
    			- Beschriftung: Online\SF-FILE2019
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\Hyper-V\Snapshots
    				- E:\Hyper-V\Virtual Hard Disks
    				- E:\Hyper-V\Virtual Hard Disks\
    				- E:\Hyper-V\Virtual Machines\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Microsoft Hyper-V VSS Writer:\Host Component"
    			- Name: Host Component
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \Host Component
    			- Beschriftung: Host Component
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    
    	* WRITER "ASR Writer"
    		- Verfasserkennung = {be000cbe-11fe-4426-9c58-531aa6355fc4}
    		- Instanzkennung = {a7f429b9-8f1b-4903-a435-06a9635c3cd1}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_IF_CAN_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = TRUE
    		- Ausgeschlossene Dateien:
    		+ Komponente "ASR Writer:\ASR\ASR"
    			- Name: ASR
    			- Logischer Pfad: ASR
    			- Vollständiger Pfad: \ASR\ASR
    			- Beschriftung: ASR
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: FALSE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    			- Von dieser Komponente betroffene Volumes:
    			- Komponentenabhängigkeiten:
    		+ Komponente "ASR Writer:\Volumes\Volume{b9dc17a6-4f94-4eaa-9ad5-f3818e527216}"
    			- Name: Volume{b9dc17a6-4f94-4eaa-9ad5-f3818e527216}
    			- Logischer Pfad: Volumes
    			- Vollständiger Pfad: \Volumes\Volume{b9dc17a6-4f94-4eaa-9ad5-f3818e527216}
    			- Beschriftung: Wählen Sie dieses Volume (\??\Volume{b9dc17a6-4f94-4eaa-9ad5-f3818e527216}) aus, wenn es sich um ein kritisches Volume handelt.
    Kritische Volumes sind solche, die durch ASR wiederhergestellt werden müssen.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    			- Von dieser Komponente betroffene Volumes:
    			- Komponentenabhängigkeiten:
    		+ Komponente "ASR Writer:\Volumes\Volume{88eeb7c7-f078-4f21-a176-cea1d474670e}"
    			- Name: Volume{88eeb7c7-f078-4f21-a176-cea1d474670e}
    			- Logischer Pfad: Volumes
    			- Vollständiger Pfad: \Volumes\Volume{88eeb7c7-f078-4f21-a176-cea1d474670e}
    			- Beschriftung: Wählen Sie dieses Volume (\??\Volume{88eeb7c7-f078-4f21-a176-cea1d474670e}) aus, wenn es sich um ein kritisches Volume handelt.
    Kritische Volumes sind solche, die durch ASR wiederhergestellt werden müssen.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: FALSE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    			- Von dieser Komponente betroffene Volumes:
    			- Komponentenabhängigkeiten:
    		+ Komponente "ASR Writer:\Volumes\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}"
    			- Name: Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}
    			- Logischer Pfad: Volumes
    			- Vollständiger Pfad: \Volumes\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}
    			- Beschriftung: Wählen Sie dieses Volume (E:) aus, wenn es sich um ein kritisches Volume handelt.
    Kritische Volumes sind solche, die durch ASR wiederhergestellt werden müssen.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    			- Von dieser Komponente betroffene Volumes:
    			- Komponentenabhängigkeiten:
    		+ Komponente "ASR Writer:\Volumes\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}"
    			- Name: Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}
    			- Logischer Pfad: Volumes
    			- Vollständiger Pfad: \Volumes\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}
    			- Beschriftung: Wählen Sie dieses Volume (C:) aus, wenn es sich um ein kritisches Volume handelt.
    Kritische Volumes sind solche, die durch ASR wiederhergestellt werden müssen.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: FALSE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    			- Von dieser Komponente betroffene Volumes:
    			- Komponentenabhängigkeiten:
    		+ Komponente "ASR Writer:\Disks\harddisk0"
    			- Name: harddisk0
    			- Logischer Pfad: Disks
    			- Vollständiger Pfad: \Disks\harddisk0
    			- Beschriftung: Schließen Sie Datenträger "0" (mit Signatur "dc3013df-635c-4719-bf00-292d75c1c09d") durch entsprechende Auswahl in die ASR-Wiederherstellung ein.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    			- Von dieser Komponente betroffene Volumes:
    			- Komponentenabhängigkeiten:
    		+ Komponente "ASR Writer:\Disks\harddisk5"
    			- Name: harddisk5
    			- Logischer Pfad: Disks
    			- Vollständiger Pfad: \Disks\harddisk5
    			- Beschriftung: Schließen Sie Datenträger "5" (mit Signatur "b3fe6281-3c8e-4e42-9e99-fb511945d87c") durch entsprechende Auswahl in die ASR-Wiederherstellung ein.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    			- Von dieser Komponente betroffene Volumes:
    			- Komponentenabhängigkeiten:
    		+ Komponente "ASR Writer:\BCD\BCD"
    			- Name: BCD
    			- Logischer Pfad: BCD
    			- Vollständiger Pfad: \BCD\BCD
    			- Beschriftung: Dies ist der Pfad zum Start-BCD-Speicher und den Start-Managern.
    Alle Dateien in diesem Verzeichnis müssen gesichert werden.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{88eeb7c7-f078-4f21-a176-cea1d474670e}\ []
    			- Komponentenabhängigkeiten:
    
    	* WRITER "Shadow Copy Optimization Writer"
    		- Verfasserkennung = {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    		- Instanzkennung = {27fad009-1262-446d-881f-c116a079f49d}
    		- Unterstützt Wiederherstellungsereignisse = TRUE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_UNDEFINED
    		- Wiederherstellungsmethode = VSS_RME_UNDEFINED
    		- Erfordert Neustart nach Wiederherstellung = FALSE
    		- Ausgeschlossene Dateien:
    
    	* WRITER "BITS Writer"
    		- Verfasserkennung = {4969d978-be47-48b0-b100-f328f07ac1e0}
    		- Instanzkennung = {9cb08863-28c7-43e3-ac8a-96caa5f1eebf}
    		- Unterstützt Wiederherstellungsereignisse = TRUE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_UNDEFINED
    		- Wiederherstellungsmethode = VSS_RME_UNDEFINED
    		- Erfordert Neustart nach Wiederherstellung = FALSE
    		- Ausgeschlossene Dateien:
    			- Exclude: Pfad = C:\ProgramData\Microsoft\Network\Downloader\, Dateispez. = *
    
    	* WRITER "Dedup Writer"
    		- Verfasserkennung = {41db4dbf-6046-470e-8ad5-d5081dfb1b70}
    		- Instanzkennung = {69a7ad26-c1ad-42f7-b57f-08cdc2bc523d}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = FALSE
    		- Ausgeschlossene Dateien:
    			- Exclude: Pfad = E:\System Volume Information\Dedup\State\, Dateispez. = *
    			- Exclude: Pfad = E:\System Volume Information\Dedup\Logs\, Dateispez. = *
    		+ Komponente "Dedup Writer:\Dedup on Volume E:\Chunk Store"
    			- Name: Chunk Store
    			- Logischer Pfad: Dedup on Volume E:
    			- Vollständiger Pfad: \Dedup on Volume E:\Chunk Store
    			- Beschriftung: Der Blockspeicher für Volume "E:". Wählen Sie ihn nur bei Verwendung der optimierten Sicherung aus.
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\System Volume Information\Dedup\ChunkStore\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    		+ Komponente "Dedup Writer:\Dedup on Volume E:\Dedup Configuration"
    			- Name: Dedup Configuration
    			- Logischer Pfad: Dedup on Volume E:
    			- Vollständiger Pfad: \Dedup on Volume E:\Dedup Configuration
    			- Beschriftung: Datendeduplizierungskonfiguration auf Volume "E:"
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- E:\System Volume Information\Dedup\Settings\
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{176501a3-50b1-47d9-ac01-ceb4439f9cc0}\ [E:\]
    			- Komponentenabhängigkeiten:
    
    	* WRITER "Registry Writer"
    		- Verfasserkennung = {afbab4a2-367d-4d15-a586-71dbb18f8485}
    		- Instanzkennung = {949bb269-865b-4ac1-a6c0-db858b877b08}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = TRUE
    		- Ausgeschlossene Dateien:
    		+ Komponente "Registry Writer:\Registry"
    			- Name: Registry
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \Registry
    			- Beschriftung: Registry
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- C:\Windows\System32\SMI\Store\Machine
    				- C:\Windows\system32\config
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    
    	* WRITER "COM+ REGDB Writer"
    		- Verfasserkennung = {542da469-d3e1-473c-9f4f-7847f01fc64f}
    		- Instanzkennung = {24509359-8d4b-42db-a6eb-e50ab1dd49ef}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
    		- Erfordert Neustart nach Wiederherstellung = FALSE
    		- Ausgeschlossene Dateien:
    		+ Komponente "COM+ REGDB Writer:\COM+ REGDB"
    			- Name: COM+ REGDB
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \COM+ REGDB
    			- Beschriftung: COM+ REGDB
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: TRUE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- C:\Windows\Registration
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    
    	* WRITER "WMI Writer"
    		- Verfasserkennung = {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    		- Instanzkennung = {667e238f-5e8a-49bf-a43e-15cfd1c00d3f}
    		- Unterstützt Wiederherstellungsereignisse = FALSE
    		- Bedingungen für Verfasserwiederherstellung = VSS_WRE_NEVER
    		- Wiederherstellungsmethode = VSS_RME_RESTORE_AT_REBOOT
    		- Erfordert Neustart nach Wiederherstellung = TRUE
    		- Ausgeschlossene Dateien:
    		+ Komponente "WMI Writer:\WMI"
    			- Name: WMI
    			- Logischer Pfad: 
    			- Vollständiger Pfad: \WMI
    			- Beschriftung: Windows Managment Instrumentation
    			- Typ: VSS_CT_FILEGROUP [2]
    			- Ist auswählbar: FALSE
    			- Auf oberster Ebene: TRUE
    			- Benachricht. nach Sicherung: FALSE
    			- Von dieser Komponente betroffene Pfade:
    				- C:\Windows\system32\wbem\repository
    			- Von dieser Komponente betroffene Volumes:
                                   - \\?\Volume{07255ba6-0afe-491e-8b73-b7320dbfec57}\ [C:\]
    			- Komponentenabhängigkeiten:
    
    Anzahl aufgeführter Verfasser: 12
    
    DISKSHADOW> exit
    ...
    
    Anzahl aufgeführter Verfasser: 12
    
    DISKSHADOW> exit
    PS C:\> find.exe /i "Th-VM" C:\Temp\writers.txt
    PS C:\> Get-Content C:\temp\writers.txt | Select-String Th-VM
    PS C:\> Get-Content C:\temp\writers.txt | Where-Object {$_ -ilike '*th-vm*'}
    PS C:\> # Th-VM is NOT in the list of writers
    PS C:\> Get-CimInstance Win32_Service -Filter "name = 'vmms'"
    
    ProcessId Name StartMode State   Status ExitCode
    --------- ---- --------- -----   ------ --------
    3260      vmms Auto      Running OK     0
    
    
    PS C:\> Get-Service vmms
    
    Status   Name               DisplayName
    ------   ----               -----------
    Running  vmms               Hyper-V-Verwaltung für virtuelle Co...
    
    
    PS C:\> Get-Service vmms | Set-Service -StartupType Disabled
    PS C:\> Stop-Service vmms
    PS C:\> # Now checking DPM
    PS C:\> # Found: After refreshing the Hyper-V host, Hyper-V is not offered any more at all in DPM
    PS C:\> Get-Service vmms | Set-Service -StartupType Automatic
    PS C:\> Start-Service vmms
    PS C:\> # Checking DPM again:
    PS C:\> # Without refreshing, the protection group shows exactly the VMs being backed up
    PS C:\> # After refreshing, Th-VM is again offered
    So it seams that DPM seems to have the idea of the Th-VM, but it does not stem from the Hyper-V host nor its VSS writers, right? So I should call into DPM support?


    Best Regards, Stefan Falk


    • Edited by Stefan Falk Friday, December 13, 2019 1:53 PM editor behaved strangely
    Friday, December 13, 2019 1:51 PM
  • Hi Stefan,

    For the 2nd test - with the Hyper-V writer (vmms) stopped, DPM should still list the Hyper-V VM's currently protected after a refresh.  Can you confirm you have at least one VM protected when you did that test. 


    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.

    Friday, December 13, 2019 4:10 PM
    Moderator
  • Hello Mike,

    Thanks for the super-fast response! Yes there are 10+ VMs in that protection group, but the whole "Hyper-V" node did not appear after stopping the vmms service and refreshing the host node in DPM. Is vmms the right service to stop or did I stop the wrong one?


    Best Regards, Stefan Falk

    Friday, December 13, 2019 4:13 PM
  • Hi Stefan

    OK - I think I need to revise my steps for test2.  Please use the new steps below.

    1) On the Hyper-V server - stop the VMMS service.
    2) On the DPM Server, modify the protection group and refresh the Hyper-V server. The Hyper-V workloads will not be listed.
    3) Cancel the Modify PG and then modify it again and now just expand the Hyper-V server without the refresh - this should now display the Hyper-V and under it list only protected VM's.  The mystery th-VM should not be listed.
    4) You can start VMMS service on the Hyper-V server again.

    Regards
    Mike Jacquet 


    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.

    Friday, December 13, 2019 5:27 PM
    Moderator
  • Hello Mike,

    I did as you described in your revised test plan 2. The results are:

    In 3), DPM does only show the VMs backed up. The Th-VM is not shown.

    Additionally, only after refreshing the host again in DPM after restarting vmms, Th-VM reappeared.

    So what should happen next?


    Best Regards, Stefan Falk

    Monday, December 16, 2019 4:43 PM
  • Hi Stefan,

    Lets do this in steps.  See if the th-VM gets listed in the output of the below DPM Powershell commands.

    1) On the DPM Server open the DPM PowerShell then enter the below command in order and change the Hyper-V_Servername accordingly.

     $guid = "66841cd4-6ded-4f4b-8f17-fd23f8ddc3de"
     $2016guid = "713b9566-8a2f-4ae6-a628-07a58c0fd0cc"
     $ps = Get-ProductionServer -DPMServerName  (&hostname) | where { $_.NetBiosName -eq "Hyper-V_Servername" }
     $dslist=Get-Datasource -ProductionServer $ps -Inquire
     $dslist | ? {$($_.Type.IsDatasource) -and (($($_.Type.Id) -match $guid) -or  ($($_.Type.Id) -match $2016guid)) -and ! $($_.Protected)}

    Is the Th-VM listed and if so does it have a componentname guid listed for it ? 

    2)  Assuming it is listed - Enable verbose logging on the Hyper-V Server - then rerun the above commands.

    a) On the Hyper-V Sever open regedit and add the following values.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager
         TraceLogLevel:Reg_Dword:0x43e

    b) When there are no active backup jobs running on the Hyper-V server stop the DPMRA service:  

        Net Stop dpmra

    c) Delete the C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\dpmracurr.errlog

    d) Re-run the DPM powershell commands on the DPM Server.

    d) After it completes open the C:\Program Files\Microsoft Data Protection Manager\DPM\Temp\dpmracurr.errlog in notepad and search for th-VM and / or componentname guid.

    e) Turn off verbose logging by removing or renaming the registry entries and stop the DPMRA service again.

    If possible share the dpmracurr.errlog one OneDrive so I can look at it.

    Regards
    mike Jacquet


    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, December 16, 2019 9:48 PM
    Moderator
  • Hello Mike,

    I did as you told me. The Th-VM showed up in the PowerShell output. The verbose dpmracurr.errlog is available under https://1drv.ms/u/s!AnuxuhxP0zblsPpVTthAwsPo83H5wQ?e=p20o7a

    Thanks for your valuable work!


    Best Regards, Stefan Falk

    Wednesday, December 18, 2019 1:15 PM
  • Hi Stefan,

    Thanks for that, I extracted the xml information that contains the bogus th-vm/ entry and it is the Hyper-V rct writer that is passing it to us.   It is strange that the diskshadow list writer did not list it however you will need to post a forum post in the Windows Hyper-V form or open a case with them. 


    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.


    Wednesday, December 18, 2019 4:30 PM
    Moderator
  • Hello Mike,

    Thank you very much for your deep analysis. For the reference, I posted here: https://social.technet.microsoft.com/Forums/en-US/d887d74f-852e-4dad-8da4-bfa373beba07/hyperv-lists-nonexistent-vm-named-thvm-to-dpm?forum=winserverhyperv


    Best Regards, Stefan Falk


    • Edited by Stefan Falk Wednesday, December 18, 2019 5:01 PM link
    Wednesday, December 18, 2019 5:00 PM