I am working on setting up Azure Site Recovery between 2 datacenters. Both sites are running Windows 2012 Hyper V cluster and VMM 2012 R2. Both sites have DC running and they are on their independent domains as follows. I have MPLS connection between the sites and able to communicate with servers on both sides.  

Site 1: primary.xzy.com

Site 2: dr.xzy.com

I am getting error while enabling protection for virtual machines running on primary site. 

---------------------------------------------------------------------------------------------------------------------------------

Job ID: 0e584228-5744-43b5-80f9-a55b2c4fae39-2015-05-19 18:51:04Z
Start Time: 5/20/2015 12:00:33 PM
Duration: 2 MINUTES

Replication couldn't be enabled for the virtual machine. (Error code: 40000)
Provider error: VMM cannot complete the host operation on the vhost01.primary.xyz.com server because of the error: Hyper-V failed to enable replication for virtual machine 'ReplicationTest': The specified target is unknown or unreachable (0x80090303). (Virtual Machine ID 762F7A23-1A2E-480B-B562-11184D6FAA7C)

Hyper-V failed to authenticate the Replica server DRReplicaBroker.dr.xyz.com using Kerberos authentication. Error: The specified target is unknown or unreachable (0x80090303)
Resolve the host issue and then try the operation again. (Provider error code: 12700)
Possible causes: Either the current replication state of the virtual machine doesn't support this operation, the recovery site configuration for the virtual machine doesnt match the configuration in the Microsoft Azure Site Recovery portal, or the Microsoft Azure Site Recovery Provider version isn't up-to-date. Check the Provider errors for more information.
Recommendation: Ensure that the latest version of the Provider is installed. If the replica virtual machine already exists, remove it. If replication is enabled verify that the recovery site selected matches the settings in Azure. Then retry the operation.

UTC Time: Wed May 20 2015 18:28:25 GMT-0400 (Eastern Daylight Time)
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36
Language: en-us
Portal Version: 5.4.00298.14 (rd_auxportal_stable.150515-0812)
PageRequestId: 111c7375-8b38-453e-a0a3-9e469af4397f
Email Address: tech@xyz.com (MSA)
Subscriptions: d3ec7a7f-c5ff-45af-8c6f-6b18c57fc0ac

---------------------------------------------------------------------------------------------------------------------------

All the hosts and VMM machine on the primary site and talk to DRReplicaBroker.dr.xyz.com

I am assuming the issue could be with Kerberos authentication but I am not too familiar with it so any help would be greatly appreciated. Also, do I need to enable replication within Hyper V Manager on each virtual machine that I want protect?? Firewalls are turned off at primary and DR site on all the host controllers. 

• Edited by milan21984 Wednesday, May 20, 2015 6:55 PM

Hi Milan21984,

Since you are using Kerberos based authentication, you need to ensure that both the domains can authenticate each other.

For a cross domain case like this, kindly use the certificate method for cloud configuration.

You can go to the protected cloud and edit the cloud configuration. Specify the authentication mechanism as certificate. 

Let us know if that resolved the problem.

Thank you,

Ruturaj

• Proposed as answer by Ruturaj DhekaneMicrosoft employee, Owner 23 hours 18 minutes ago
• Marked as answer by milan21984 15 hours 32 minutes ago

Hi Milan21984,

Since you are using Kerberos based authentication, you need to ensure that both the domains can authenticate each other.

For a cross domain case like this, kindly use the certificate method for cloud configuration.

You can go to the protected cloud and edit the cloud configuration. Specify the authentication mechanism as certificate. 

Let us know if that resolved the problem.

Thank you,

Ruturaj

• Proposed as answer by Ruturaj DhekaneMicrosoft employee, Owner 23 hours 22 minutes ago
• Marked as answer by milan21984 15 hours 36 minutes ago

Hi Milan21984,

Since you are using Kerberos based authentication, you need to ensure that both the domains can authenticate each other.

For a cross domain case like this, kindly use the certificate method for cloud configuration.

You can go to the protected cloud and edit the cloud configuration. Specify the authentication mechanism as certificate. 

Let us know if that resolved the problem.

Thank you,

Ruturaj

• Proposed as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, May 21, 2015 7:57 AM
• Marked as answer by milan21984 Thursday, May 21, 2015 3:43 PM

Thanks for getting back to me. This fix was much easier than I thought. I logged onto my Azure portal and changed the configuration of the Cloud to use certificate method and it actually created certificate on all my primary and secondary sites and applied to all the host controllers. 



After getting that done, I restarted the job to enable replication and that time I got different error message. 

-----------------------------------------------------------------------------------------------------------

Job ID: 0e584228-5744-43b5-80f9-a55b2c4fae39-2015-05-19 18:51:04Z
Start Time: 5/21/2015 9:15:48 AM
Duration: 2 MINUTES

DRA could not prepare for initial replication. (Error code: 25035)
Provider error: A virtual machine with Hyper-V ID (762f7a23-1a2e-480b-b562-11184d6faa7c) couldn't be found in cloud f00d532a-315d-4350-8866-c4040bfb0a70.
Ensure that the virtual machine is located in the cloud. (Provider error code: 31230)
Possible causes: Check the Provider error for more information.
Recommendation: Resolve the issue and retry the operation.

UTC Time: Thu May 21 2015 15:48:16 GMT-0400 (Eastern Daylight Time)
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36
Language: en-us
Portal Version: 5.4.00298.14 (rd_auxportal_stable.150515-0812)
PageRequestId: 50cb118f-090c-4298-81b8-8cda66f5f1b2
Email Address: tech@xyz.com (MSA)
Subscriptions: d3ec7a7f-c5ff-45af-8c6f-6b18c57fc0ac

----------------------------------------------------------------------------------------

Above error was fixed by installing UR4 for Virtual Machine Manager 2012 R2 (SCVMM).

https://support.microsoft.com/en-us/kb/2992024

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 12 hours 10 minutes ago

Thanks for getting back to me. This fix was much easier than I thought. I logged onto my Azure portal and changed the configuration of the Cloud to use certificate method and it actually created certificate on all my primary and secondary sites and applied to all the host controllers. 



After getting that done, I restarted the job to enable replication and that time I got different error message. 

-----------------------------------------------------------------------------------------------------------

Job ID: 0e584228-5744-43b5-80f9-a55b2c4fae39-2015-05-19 18:51:04Z
Start Time: 5/21/2015 9:15:48 AM
Duration: 2 MINUTES

DRA could not prepare for initial replication. (Error code: 25035)
Provider error: A virtual machine with Hyper-V ID (762f7a23-1a2e-480b-b562-11184d6faa7c) couldn't be found in cloud f00d532a-315d-4350-8866-c4040bfb0a70.
Ensure that the virtual machine is located in the cloud. (Provider error code: 31230)
Possible causes: Check the Provider error for more information.
Recommendation: Resolve the issue and retry the operation.

UTC Time: Thu May 21 2015 15:48:16 GMT-0400 (Eastern Daylight Time)
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36
Language: en-us
Portal Version: 5.4.00298.14 (rd_auxportal_stable.150515-0812)
PageRequestId: 50cb118f-090c-4298-81b8-8cda66f5f1b2
Email Address: tech@xyz.com (MSA)
Subscriptions: d3ec7a7f-c5ff-45af-8c6f-6b18c57fc0ac

----------------------------------------------------------------------------------------

Above error was fixed by installing UR4 for Virtual Machine Manager 2012 R2 (SCVMM).

https://support.microsoft.com/en-us/kb/2992024

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 12 hours 6 minutes ago

So now that I was able to properly configure the Azure Site Recovery portal and also successfully replicated a test VM, I have few questions regarding the networking piece of it. All the VMs that are running on primary site have 2 networks configured on them. Some of them are web servers with more than one static IPs configured for the sites being hosted on those servers. How can I configure those VMs so that when they start up at the DR site, they have all the right configuration and also joined to the domain at the DR site. I also have load balancers configured at the DR site so they depend on certain static IP addresses to bring up the services. 

Any resources of help you can offer would be greatly appreciated. Also please send me the video links if available that explains this topic little more in detail. Thanks. 

Thanks for getting back to me. This fix was much easier than I thought. I logged onto my Azure portal and changed the configuration of the Cloud to use certificate method and it actually created certificate on all my primary and secondary sites and applied to all the host controllers. 



After getting that done, I restarted the job to enable replication and that time I got different error message. 

-----------------------------------------------------------------------------------------------------------

Job ID: 0e584228-5744-43b5-80f9-a55b2c4fae39-2015-05-19 18:51:04Z
Start Time: 5/21/2015 9:15:48 AM
Duration: 2 MINUTES

DRA could not prepare for initial replication. (Error code: 25035)
Provider error: A virtual machine with Hyper-V ID (762f7a23-1a2e-480b-b562-11184d6faa7c) couldn't be found in cloud f00d532a-315d-4350-8866-c4040bfb0a70.
Ensure that the virtual machine is located in the cloud. (Provider error code: 31230)
Possible causes: Check the Provider error for more information.
Recommendation: Resolve the issue and retry the operation.

UTC Time: Thu May 21 2015 15:48:16 GMT-0400 (Eastern Daylight Time)
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36
Language: en-us
Portal Version: 5.4.00298.14 (rd_auxportal_stable.150515-0812)
PageRequestId: 50cb118f-090c-4298-81b8-8cda66f5f1b2
Email Address: tech@xyz.com (MSA)
Subscriptions: d3ec7a7f-c5ff-45af-8c6f-6b18c57fc0ac

----------------------------------------------------------------------------------------

Above error was fixed by installing UR4 for Virtual Machine Manager 2012 R2 (SCVMM).

https://support.microsoft.com/en-us/kb/2992024

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Thursday, May 21, 2015 7:09 PM

Any update on my last error on this posting?? I am still experiencing this error with Windows 2012 VM and Windows 2008 R2 VM.

Finally, I was able to figured out a solution to this error message. What a breakthrough.

I was getting constant failure messages in the Azure portal when I tried to enable protection for a virtual machines. I Also tried refreshing the virtual machine from SCVMM as Ruturaj suggested previously within this post, I received a totally different error message in Azure portal. Basically, what was happening is when I enabled the protection for a virtual machine, it initiated the process of creating a virtual machine at the secondary SCVMM site but it was quickly failing and I was getting failed status for that VM. Looking back at my previous error message, now it makes sense that it was targeted for the secondary site. In the end, I think that the error message is poorly worded and it doesn't provide a whole lot of insight. 

In order to over come this error message, in the secondary SCVMM, simply right click on the virtual machine and click Repair. Choose the Ignore option and click repair. After the repair process is successfully completed, you will see Completed status under the Job Status column. At this point, simply restart the protection job in Azure portal and it will complete the job successfully. You will be able to see the replication status within the Hyper V Manager for that VM.

Hope this makes sense. Feel free to comment if I can clarify anything.

• Marked as answer by milan21984 11 hours 26 minutes ago

Finally, I was able to figured out a solution to this error message. What a breakthrough.

I was getting constant failure messages in the Azure portal when I tried to enable protection for a virtual machines. I Also tried refreshing the virtual machine from SCVMM as Ruturaj suggested previously within this post, I received a totally different error message in Azure portal. Basically, what was happening is when I enabled the protection for a virtual machine, it initiated the process of creating a virtual machine at the secondary SCVMM site but it was quickly failing and I was getting failed status for that VM. Looking back at my previous error message, now it makes sense that it was targeted for the secondary site. In the end, I think that the error message is poorly worded and it doesn't provide a whole lot of insight. 

In order to over come this error message, in the secondary SCVMM, simply right click on the virtual machine and click Repair. Choose the Ignore option and click repair. After the repair process is successfully completed, you will see Completed status under the Job Status column. At this point, simply restart the protection job in Azure portal and it will complete the job successfully. You will be able to see the replication status within the Hyper V Manager for that VM.

Hope this makes sense. Feel free to comment if I can clarify anything.

• Marked as answer by milan21984 11 hours 32 minutes ago

Finally, I was able to figured out a solution to this error message. What a breakthrough.

I was getting constant failure messages in the Azure portal when I tried to enable protection for a virtual machines. I Also tried refreshing the virtual machine from SCVMM as Ruturaj suggested previously within this post, I received a totally different error message in Azure portal. Basically, what was happening is when I enabled the protection for a virtual machine, it initiated the process of creating a virtual machine at the secondary SCVMM site but it was quickly failing and I was getting failed status for that VM. Looking back at my previous error message, now it makes sense that it was targeted for the secondary site. In the end, I think that the error message is poorly worded and it doesn't provide a whole lot of insight. 

In order to over come this error message, in the secondary SCVMM, simply right click on the virtual machine and click Repair. Choose the Ignore option and click repair. After the repair process is successfully completed, you will see Completed status under the Job Status column. At this point, simply restart the protection job in Azure portal and it will complete the job successfully. You will be able to see the replication status within the Hyper V Manager for that VM.

Hope this makes sense. Feel free to comment if I can clarify anything.

• Marked as answer by milan21984 Wednesday, June 10, 2015 7:46 PM