Test-Failover of Recovery Plan is failing

Category: microsoft azure site recovery


Cemál on Thu, 29 Oct 2015 09:21:21

I have been able to perform test fail overs up until this week, they are now failing. Below are the details of the error's received and the JOB ID.

I would appreciate some assistance with this!

Job ID

1ac9a932-cee8-43b0-8d3e-58e20f03c864-2015-10-27 10:15:04Z

Errors (2)

The operation was stopped. (Error code: 70080) Copy  

Possible causes The Azure operation timed out or a manual user action was pending for too long.
Recommendation Resolve the issue and retry the operation.

The requested action couldn't be performed by the 'Hyper-V Replica To Azure' Replication Provider. (Error code: 539) Copy  

Possible causes The Provider action failed. Check other errors for more information.
Recommendation Resolve the issue and retry the operation.

Kind Regards,



Cemál on Thu, 29 Oct 2015 16:26:29

The VM in question is a linux vm, one NIC with Static IP and another with DHCP. For some reason the second nic was not picking up DHCP during fail over and this was causing it to fail. Configuring a static ip at the vm config properties in Site Recovery on Azure is being used as a workaround atm while this being investigated.

Ruturaj Dhekane on Tue, 08 Dec 2015 10:00:32

Hi Cemal, It seems you hit an issue that was an intermittent bug in the system. We have fixed it now.

Let me know if you are still facing the issue.

Thank you,


Rampant Tech on Sun, 20 Dec 2015 03:13:01

Hi Mate,

I am having the same issue. I have a recovery plan which has been working for a few weeks. ( I have been running it and completed several test fail overs into the Basic Server environment IE: (using A3 Basic Servers. )

I failed over a few times last week all was good and I am writning the internal process for this all.

On the 17th Dec I changed the servers from Basic A3 to DS3 ( I did this for the SQL servers mainly so they would be quicker and decided to have them all the same )

Now since the 17Th one server ceased to be able to be failed over to. It just keeps errorring "The
operation was stopped. (Error code: 70080) ". It replicates fine. Once on Friday ( qld aussie time ) after the failed fail over it had to re replicated everything due to an inconsistent blob error??.

Since then It has replicated back all fine, but failover is still failing with the above error. This server has 3 x 1023 GB HDD's in a storage pool.
Replication up to Azure is fine, failover was working.

All I changed is I went from Basic PC's to DS3 Machines. As it was too slow in the Basic PC's where I had been testing it all.

Now we are ready to make this the full DS Site. I want the real Productions Machines and speeds tested etc.

Any help would be really nice

Regards Rampant Tech