@Benjamin Cramphorn Appreciate your patience in this matter.
"Sharing the solution with broader community" Cause: While trying to trigger a backup for the VM from the MABS server it crashes the DPM service. Because, the old VM ID was syncing with Database and causing backup failures
Solution: Created a new VM, and attached the same VHDs from the old VMs, before this stopped the protection and deleted the data from DPM console, then created a new VM on Hyper-V and attached the old VHDs. Tried protecting new VM which created new object ID in DPM database. The necessity of this was because we need to create a fresh VM ID to be updated in the DPM database, as for the old one it was already protected and each time, we try to re-protect it from scratch, it’s still synching with the old VM ID.
If the response helped, do "Accept Answer" and up-vote it