We are trying to do a proof of concept of DR a small server to Azure to see if it's a viable DR solution.

All goes fairly well in the Azure setup and on the System Center Virtual Machine Manager configuration.

But when we try to enable replication we always get this error after about 10 minutes.

 

 

ERRORS (1)

 

 

 

Protection couldn't be enabled for the virtual machine. (Error code: 70094)

 

 

 

 

 

Provider error

 

Unable to complete the request. Operation on the nnnnn.xxx.local server timed out.
Try the operation again. (Provider error code: 2924)

 

 

 

Possible causes

 

Protection can't be enabled with the virtual machine in its current state. Check the Provider errors for more information.

 

 

 

Recommendation

 

Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host server. If this virtual machine is enabled for replication on the Hyper-V host, disable this setting. Then try to enable protection again.

 

 

 

 

 

 

nnnnn.xxx.local is the FQDN of the Hyper-V host, not the guest we are trying to replicate (is that the correct machine?)

However in the dashboard it's clear that Azure is trying to replicate our test server.



The redacted (!) server name here is the name of the server that we are trying to replicate.

We have tested Internet connectivity on all the relevant machines and they seem fine.

On the Hyper-V host we can see this message in the Event Viewer

Enable replication failed for virtual machine 'XXXXDR' due to a network communication failure. (Virtual Machine ID d1b39ef4-e761-4faf-9286-8057b360a620, Data Source ID 0, Task ID 4a713364-e7ca-4c3c-b807-834248c51774)

Note that for various reasons we had to choose Southeast Asia for the location of the Storage Account and Azure Site Recovery Vault because there is no option to choose an Australian location for the Storage Account, only Azure Site Recovery Vault and both have to be in the same location for site replication to Azure

Thanks