vRA 8.3: Error Detail: This resource no longer exists in the deployment.

[DeanLiu]

How to resolve the issue that missing VM instance, after restore VM in vRA.
Steps to repro:
1. Deploy a Cloud Template.

2. Backup the VM.

3. Restore the VM.  

3.1. I make sure before and after Restore, there are the same uuid to target vm. 

Expect result: restore VM successfully without any warning or errors.
Actually result: Restore VM successfully, but VM show an error "This resource no longer exists in the deployment". And all of day-2 actions are changed to “unavailable”

[paul_xtravirt]

When you have restored the vm from backup, what happens if you onboard the VM?

[DeanLiu]

Hi Paul, thanks for your reply. I have got the root cause. vRA platform is not only using the instance uuid and bios uuid to distinguish a vm, also using the MoRef Id. In fact, in my case, after restored, the MoRef Id has been changed, even if the instance uuid and bios uuis are retained.

I don't know how to give you awarding points, but I can mark your answer as correct answer.

In fact, I want to give myself some awarding points, too. 😁

Thanks,

Dean

[gbeke]

Hi @DeanLiu, 

I've the same situation with vRA 8.9.1. Did you manage to solve it, if so how? Doing onboarding seems to create a new deployment which is not what we need. We need the vm to appear in the original deployment.

Thanks.

Gaute

[hb302]

Same here. I onboarded the VM into a new deployment. Can the old deployment be safely deleted without deletion of the VM?