Hi all,

I have a test scenario where we have set up a small domain (4 servers DC, Web, Sql and another) on one host and protected in ASR 3 (all except the dc) of the four. We have a VPN into Azure and a DC sitting in the Azure network. We tried a few test scenarios and most went well but we decided to disconnect the original host on premise and bring up a new host to simulate a complete hardware failure. 

When I go to fail the machines over from Azure to the new server on premises it says. You've chosen a different Hyper-V server for failover. To keep data consistent make sure the original server isn't currently in the Hyper V-Site.

However, when you try to remove the server from the Hyper-V site.

I am just wondering what exact method I should be using. What is the correct process for this type of recovery. I know the message says disable protection but I just want to check before I press the button.

Cheers,

G

Hi Gavin,

Removing protection deletes  the placeholder virtual machine on the recovery site. If you remove protection   from a virtual machine, the states of the virtual machine and the protection  group are set to Not Configured. Running a recovery plan that contains the   protection group succeeds, but site Recovery Manager does not recover the virtual machines that are in the Not Configured state.

However, you may Click Yes to confirm the removal of protection from the virtual machine.

Regards,

Shirisha Paderu

Hi Gavin,

Removing protection deletes  the placeholder virtual machine on the recovery site. If you remove protection   from a virtual machine, the states of the virtual machine and the protection  group are set to Not Configured. Running a recovery plan that contains the   protection group succeeds, but site Recovery Manager does not recover the virtual machines that are in the Not Configured state.

Regards,

Shirisha Paderu

• Edited by Shirisha PaderuMicrosoft contingent staff, Moderator 20 hours 55 minutes ago

Hi Gavin,

Removing protection deletes  the placeholder virtual machine on the recovery site. If you remove protection   from a virtual machine, the states of the virtual machine and the protection  group are set to Not Configured. Running a recovery plan that contains the   protection group succeeds, but site Recovery Manager does not recover the virtual machines that are in the Not Configured state.

Regards,

Shirisha Paderu

• Edited by Shirisha PaderuMicrosoft contingent staff, Moderator 20 hours 59 minutes ago

Hi Gavin,

Removing protection deletes  the placeholder virtual machine on the recovery site. If you remove protection   from a virtual machine, the states of the virtual machine and the protection  group are set to Not Configured. Running a recovery plan that contains the   protection group succeeds, but site Recovery Manager does not recover the virtual machines that are in the Not Configured state.

Regards,

Shirisha Paderu

• Edited by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM

Hi Gavin,

Removing protection deletes  the placeholder virtual machine on the recovery site. If you remove protection   from a virtual machine, the states of the virtual machine and the protection  group are set to Not Configured. Running a recovery plan that contains the   protection group succeeds, but site Recovery Manager does not recover the virtual machines that are in the Not Configured state.

Regards,

Shirisha Paderu

• Edited by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM

Hi Gavin,

Removing protection deletes  the placeholder virtual machine on the recovery site. If you remove protection   from a virtual machine, the states of the virtual machine and the protection  group are set to Not Configured. Running a recovery plan that contains the   protection group succeeds, but site Recovery Manager does not recover the virtual machines that are in the Not Configured state.

Regards,

Shirisha Paderu

• Edited by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM

Hi Gavin,

Removing protection deletes  the placeholder virtual machine on the recovery site. If you remove protection   from a virtual machine, the states of the virtual machine and the protection  group are set to Not Configured. Running a recovery plan that contains the   protection group succeeds, but site Recovery Manager does not recover the virtual machines that are in the Not Configured state.

Regards,

Shirisha Paderu

• Edited by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

Hi Anoop,

Thanks for that. I will try that now and report back. Thats a good clarification which is really what we wanted so we were testing best practice when building are recovery plans.

Cheers,

Gavin

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

• Proposed as answer by Shirisha PaderuMicrosoft contingent staff, Moderator 20 hours 54 minutes ago

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

• Proposed as answer by Shirisha PaderuMicrosoft contingent staff, Moderator 20 hours 59 minutes ago

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

• Proposed as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM
• Marked as answer by Shirisha PaderuMicrosoft contingent staff, Moderator 21 hours 9 minutes ago

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

• Proposed as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM
• Marked as answer by Shirisha PaderuMicrosoft contingent staff, Moderator 21 hours 14 minutes ago

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

• Proposed as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM
• Marked as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Wednesday, June 03, 2015 10:04 AM

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

• Proposed as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM
• Marked as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Wednesday, June 03, 2015 10:04 AM

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

• Proposed as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM
• Marked as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Wednesday, June 03, 2015 10:04 AM

Hello Gavin,

Sorry the error message has a missing phrase. Thanks for reporting this issue to us. The error message basically should say To keep the data consistent ensure that the original server is no longer communicating with the Hyper-V site. We will get the warning message fixed up in the next revision of the service. The reason we give the warning to the customers is because if the original host is still communicating (and it has the old VM on it), it could cause a split-brain situation where we have 2 versions of the same VM running in your environment.

That said this above message is only a warning message its not a blocking error message -> you still can continue to failover the machine to an alternate host. (please do not remove protection for the VMs)

Once all the VMs have failed over to the new host you can then go ahead and delete the original host from the site.

Regards,

Anoop KV

• Proposed as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Tuesday, June 02, 2015 10:18 AM
• Marked as answer by Shirisha PaderuMicrosoft contingent staff, Moderator Wednesday, June 03, 2015 10:04 AM