I have a VMWare environment connected to ASR. I have successfully "Unplanned" a failover to migrate it to the cloud. I have followed the steps provided by this documentation (https:// azure.microsoft.com/en-us/documentation/articles/site-recovery-failback-azure-to-vmware/) to fail the host back to the source environment but I get tied up at the Readiness Checks.  My host within Azure does not pass the VX and FX agent readiness checks.  Since I am using ASR, I do not seem to have the same web fronts directly to the CS that I had in the standalone setup.

How do I re-initiate the VX and FX agents to migrate the host back to on-prem?

I've just validated that the FX and VX agents are running within services.msc on the host currently in Azure to be migrated back to VMWare.

Hi Kevin.

Please make sure that recovered server in Azure communicate with CS IP. 

Thx-Gopi

Confirmed. The host in Azure can communicate with the CS via IP address.

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator 15 hours 31 minutes ago

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator 15 hours 35 minutes ago

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke 13 hours 30 minutes ago

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke 13 hours 35 minutes ago

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 22 hours 55 minutes ago
• Unmarked as answer by Ruturaj DhekaneMicrosoft employee, Owner 22 hours 55 minutes ago

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM
• Unmarked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM
• Unmarked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM
• Unmarked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM

Assisted Kevin offline and the reverse replication to onprem is in progress, after which Recovery to onprem should be performed.

• Marked as answer by Shashank PMicrosoft employee, Moderator Thursday, June 25, 2015 3:42 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM
• Unmarked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke 13 hours 30 minutes ago
• Unmarked as answer by Kevin Van Dyke 13 hours 23 minutes ago

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke 13 hours 35 minutes ago
• Unmarked as answer by Kevin Van Dyke 13 hours 28 minutes ago

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:50 PM

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:50 PM

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:50 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 22 hours 55 minutes ago

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:50 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:50 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:50 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM

Just a follow-up for any one who may have this issue in the future:

Solution not was not found. I was informed the logs showed proper behavior.  However, a different virtual machine within the same, unmodified environment was able to migrate to Azure and then back to on-prem.  The issue was not able to be reproduced and therefore not able to be solved for that particular VM.

• Marked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:43 PM
• Unmarked as answer by Kevin Van Dyke Thursday, July 23, 2015 5:50 PM
• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, July 30, 2015 8:20 AM

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke 13 hours 27 minutes ago Added Information

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke 13 hours 22 minutes ago Added Information

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke Thursday, July 23, 2015 5:51 PM Added Information

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke Thursday, July 23, 2015 5:51 PM Added Information

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke Thursday, July 23, 2015 5:51 PM Added Information

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke Thursday, July 23, 2015 5:51 PM Added Information

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke Thursday, July 23, 2015 5:51 PM Added Information

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke Thursday, July 23, 2015 5:51 PM Added Information

Almost a month later, on InMage 8.3.0, with a completely brand new environment I have run into this issue once again and followed all of the same troubleshooting paths.  I had even been able to configure a machine prior to this one for protection.

I am currently spinning up yet another VM to test reproduction.

• Edited by Kevin Van Dyke Thursday, July 23, 2015 5:51 PM Added Information

I spun up a new VM, ran it through the entire failover/back process and again, I was unable to replicate the same failures.

After spinning up a new VM, I was able to migrate.

To clarify, I have not been able to get either first VM failed back, only the new VMs.