ASR Vmware vm greyed out with message "VMware tools are not installed for the selected VM"

Question

we are testing vmware on prime machine to cloud using ASR, the vm failed over to cloud but unable to fail back to on prim. subsequently deleted the cloud vm and started on prim vm and uninstalled mobility client etc, but the machine shows on ASR as "VMware tools are not installed for the selected VM" and unable to select for replication. the machine cloned with different SID still same. How we can clear any residual configuration data and start replicate again..

Answer 1

Re installed the agent manually so it registered to the process server, now I am able to replicate the machine,

https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview

the process server deployment error further investigation lead to subscription quota issue, the server template requires 8 core but our subscription supports on 4 core now, the error detail given below

eyJ1cmwiOiAiaHR0cHM6Ly92c2Vydi1zZW50bmwwMS5hamUuYWUiLCAic2l0ZV9rZXkiOiAiYTA5YjUwMWY1NmY5ZThjYiJ9statusMessage": "{\"error\":{\"code\":\"InvalidTemplateDeployment\",\"message\":\"The template deployment 'AsrPsDeploy-test-v01' is not valid according to the validation procedure. The tracking id is '656cd198-4386-421b-a5f6-995634df8902'. See inner errors for details.\",\"details\":[{\"code\":\"QuotaExceeded\",\"message\":\"Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: UAENorth, Current Limit: 4, Current Usage: 0, Additional Required: 8, (Minimum) New Limit Required: 8. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/CapacityExperienceBlade/Parameters/

Answer 2

further verification this is caused by limitation on trial subscription, the process server requires 8 core server but subscription service supports only 4 core..

eyJ1cmwiOiAiaHR0cHM6Ly92c2Vydi1zZW50bmwwMS5hamUuYWUiLCAic2l0ZV9rZXkiOiAiYTA5YjUwMWY1NmY5ZThjYiJ9statusMessage": "{\"error\":{\"code\":\"InvalidTemplateDeployment\",\"message\":\"The template deployment 'AsrPsDeploy-test-v01' is not valid according to the validation procedure. The tracking id is '656cd198-4386-421b-a5f6-995634df8902'. See inner errors for details.\",\"details\":[{\"code\":\"QuotaExceeded\",\"message\":\"Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: UAENorth, Current Limit: 4, Current Usage: 0, Additional Required: 8, (Minimum) New Limit Required: 8. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/CapacityExperienceBlade/Parameters/

Answer 3

Hello @Suhail TV ,

Thank you for reaching out with this query.

Looking at the issue description, i understand that the previous ASR replication flow has been broken post failover, the failback workflow was not followed as per the recommended steps available in ASR failback document : https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-prepare-failback, which landed it in this issue.

In this situation, you need to follow the below procedure.

1. Disable replication from Recovery Services vault->Replicated items blade. Or you can follow the steps from https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-manage-registration-and-protection#disable-protection-for-a-vmware-vm-or-physical-server-vmware-to-azure
   If already disabled, you can proceed with the step 2.
2. ASR replications stale entry clean up can be done from the Mysql db using cmdline(MYSQL is the database of the configuration server of ASR)
   Follow the steps available at the following link to do stale entry cleanup from configuration server https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-troubleshoot-configuration-server#remove-the-stale-entries-for-protected-items-from-the-configuration-server-database
3. Once the stale entry clean up is done, you can refresh the configuration server from ASR vault->site recovery infrastructure->configuration servers blade.
4. Enable replication from scratch for the same VM.

Hope it helps!!!

Please "Accept as Answer" if any of above helped so that, it can help others in community looking for remediation for the similar issues.