Have you ever seen a deployed virtual machine in the vRA portal have its status changed to ‘Missing‘? This can happen for two reasons; The first, obvious reason, is that the source virtual machine has been deleted. Not much you can do about that except re-provision it or restore the vm from backup. The second reason, is because the reference information that vRA holds about the virtual machine is no longer valid (perhaps from an earlier restore).
In this post, I will discuss and provide a solution that will address the latter for a vSphere hosted virtual machine.
When in this state, you will not be able to perform day 2 actions on this virtual machine (apart from destroy).
The following scenarios can explain why vRA has incorrect reference data about the virtual machine:
- The virtual machine has been recovered from backup and a new instance uuid has been created;
- The virtual machine has moved to another vCenter Server, maybe during a DR event. I know that Zerto will create a new virtual machine at the DR site which will have a different instance uuid (SRM’s shadow VMs are most likely similar but I can’t confirm);
- The virtual machine was cloned and the original has been deleted;
- The instance uuid for the virtual machine has been changed, either manually or by some other process.