Summary
After a virtual machine is vMotioned from one ESXi to another, you get the "Virtual Machine unprotected after move to another ESX" error.
Details
A VM can become unprotected in any of these scenarios:
- If a VM is vMotioned by Distributed Resource Scheduler (DRS) from an ESXi protected by a Deep Security Virtual Appliance (DSVA) to an ESXi that is also protected by a DSVA, the VM will be protected automatically. Except for quarantined files, all the related files will be replicated to the receiving DSVA and then the VM will be protected again.
If you are getting the error, this could be due to DSM checking the status of the VM before all the files are replicated from one DSVA to the receiving DSVA. You can ignore the error or clear it manually by doing the following:
- On the DSM console, click Computers tab.
- In the computers list, right-click the target computer or VM.
- Select Actions > Clear Warnings/Errors to clear up the error messages.
- If a VM is vMotioned by DRS from an ESXi protected by a DSVA to an ESXi that is not protected by a DSVA, the virtual machine will become unprotected. If the VM is subsequently vMotioned back to the original ESXi, it will not automatically be protected again unless you have created an event-based task to activate and protect computers that have been vMotioned to an ESXi with an available DSVA. If you have not created such an event-based task prior to vMotioning, you have to activate the protection manually. To do this, go to the DSM console, right-click the VM and then click Actions > Activate/Reactivate.
