Hi, I recently add one host server (HOST5) in running system center 2019 DPM. I successfully add 12 VM among of 13 but only one VM (XYZPama) is not showing on Hyper-v VM's list. Previously this VM (XYZPama) was added in HOST2, so we just moved on HOST5 as well as removed it from the agent protection group(Host2.1). can anyone suggest to me- how it can be discovered or found in such a list?

Hi @Deepak Singh Baghela , Was this particular virtual machine (VM) that was running on HOST2 also protected in DPM 2019? Also what Hyper-V configuration version is the problematic VM running? The configuration version can be checked as follows: Get-VM * | Format-Table Name, Version Have you tried clicking the Refresh button which can be found on your screenshot, select one host at the time and then click "Refresh" and see if it helps. ---------- If the reply was helpful please don't forget to upvote and/or accept as answer , thank you! Best regards, Leon

This is an old question and you already accepted an answer.. still, I just googeld it. For me, I moved VMs to the new host. As for DPM, they were still protected on the old host - just missing. I kept the VM ID. After removing them manually on the DPM server from the old VM, they showed up on refresh on the DPM server and I could properly add them under the new Hyper-V host.

VM are not dicovering in an agent protection group of DPM 2019

Accepted answer

Leon Laude 85,651 Reputation points

2021-11-23T11:33:27.34+00:00

Hi @Deepak Singh Baghela ,

Was this particular virtual machine (VM) that was running on HOST2 also protected in DPM 2019?

Also what Hyper-V configuration version is the problematic VM running? The configuration version can be checked as follows: Get-VM * | Format-Table Name, Version

Have you tried clicking the Refresh button which can be found on your screenshot, select one host at the time and then click "Refresh" and see if it helps.

----------

If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!

Best regards,
Leon
Please sign in to rate this answer.
Deepak Singh Baghela 21 Reputation points

2021-11-23T13:41:09.14+00:00

Hi LeonLaude,

Thanks for the reply.
At previous that particular VM was a part of HOST2, lack of memory on HOST2 we just export the VM and move on HOST5. It's running well. I think DPM is not releasing caches or maybe any old record or any other thing.
As per your suggestion, I got the Hyper-V configuration version as below. I found that particular VM version is 8.0.

Now, what next ? that I can resolve the problem

Leon Laude 85,651 Reputation points

2021-11-23T14:25:00.647+00:00

Was the VM backed up in DPM previously when it was hosted on HOST2?

Did you try the Refresh as I mentioned?

Deepak Singh Baghela 21 Reputation points

2021-11-23T18:00:18.037+00:00

Yes, it was, but I removed it from Host2. and refreshed the all Protection groups.

Deepak Singh Baghela 21 Reputation points

2021-11-23T18:25:16.74+00:00

Hi,

May it be an operating system version issue? because Host2 has Windows server 2016, Hyper-v is 8.0 and Host5 has Windows Server 2019, Hyper-v 9.0.

Leon Laude 85,651 Reputation points

2021-11-23T18:37:19.07+00:00

DPM 2019 is able to backup Hyper-V VMs running on Windows Server 2016 as well, when you exported the VM, did you create a new ID then or copy the existing ID?

You could also try upgrading the Hyper-V configuration version with the following PowerShell command:
Update-VMVersion "VM name"

Deepak Singh Baghela 21 Reputation points

2021-11-23T19:13:44.423+00:00

I just export the VM from Host2 and create it on Host5 without changing any single word in the name. Should I create a new ID? frankly speaking, I don't have deep knowledge about it, but definitely, I made mistake in entire this process.
Finally, I want to solve it.

Does it safe to update the VM version at the currently running host? I have little confusion after reading this-

https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server#what-happens-if-i-dont-upgrade-the-virtual-machine-configuration-version

Leon Laude 85,651 Reputation points

2021-11-23T19:23:28.37+00:00

Upgrading the Hyper-V configuration version from 8 to 9 will mean that you can no longer run the VM on a Windows Server 2016 host.

When you import a Hyper-V virtual machine, you have three options:

Register in-place – This type assumes export files are in the location where you'll store and run the virtual machine. The imported virtual machine has the same ID as it did at the time of export. Because of this, if the virtual machine is already registered with Hyper-V, it needs to be deleted before the import works. When the import has completed, the export files become the running state files and can't be removed.

Restore the virtual machine – Restore the virtual machine to a location you choose, or use the default to Hyper-V. This import type creates a copy of the exported files and moves them to the selected location. When imported, the virtual machine has the same ID as it did at the time of export. Because of this, if the virtual machine is already running in Hyper-V, it needs to be deleted before the import can be completed. When the import has completed, the exported files remain intact and can be removed or imported again.

Copy the virtual machine – This is similar to the Restore type in that you select a location for the files. The difference is that the imported virtual machine has a new unique ID, which means you can import the virtual machine to the same host multiple times.

Perhaps you could try exporting the VM again, and then import it by creating a new ID, this won't affect the VM itself.
Sign in to comment

VM are not dicovering in an agent protection group of DPM 2019

1 additional answer