I have a Recovery Plan in Azure Site Recovery. On Jun 29, the Test Failover on the recovery plan finishes successfully.

However, when I try to start the Test Failover on July 7 (no changes have been made to my Azure account), it immediately fails, with the errror "Please try again. If the problem persists, contact support.".  I checked Recovery Job, there is no job created there

When I try deleting the Recovery Plan, it failed at once with error msg "Could not delete recovery plan 'XXXXXX' because an action is in progress. Verify that no actions are pending

I checked everywhere in the Azure Management Portal. There is no running or pending jobs.

Could you help me identify the issue? Your help is very much appreciated. Thanks

Stephen

Hi Stephen,

Thanks for posting here.

I suggest you to check this link for details.

http://azure.microsoft.com/blog/2014/09/04/networking-infrastructure-setup-for-microsoft-azure-as-a-disaster-recovery-site/

Girish Prajwal

Hi Girish,

Thanks for your reply. I've already read this document. But my problem is that my Recovery Plan used to work with Test Failover. But now both of my recovery plans cannot start Test Failover. Neither can I delete them. 

Both immediately fails. The delete results in an error "Could not delete recovery plan 'virtualmin-situate-ca' because an action is in progress. Verify that no actions are pending"

It seems something is still running behind the scene. But cannot find what it is.

Could you help me look deeper into this issue?

Thanks

Stephen

Hi Stephen, could you please try again?

If the issue occurs once more - could you please press Ctrl+Alt+A on the portal - it will launch a diagnostic windows.

If you could copy it and send it to ruturajd@microsoft.com, we will take a look.

Thank you,

Ruturaj

 

Hi Ruturaj,

I've sent the information you required to your email. Could you let me know what is wrong with my account that I cannot delete my recovery plan.

Thanks

Stephen

We are looking into this issue offline. There seems to be a bug in the service and we are looking at fixing it.

For all others , If you hit this issue, kindly create a new recovery plan with the same number of VMs. Try to failover the new recovery plan instead of the stuck RP.

Will update the thread when we fix this issue.

Thank you,

Ruturaj

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner 21 hours 4 minutes ago

We are looking into this issue offline. There seems to be a bug in the service and we are looking at fixing it.

For all others , If you hit this issue, kindly create a new recovery plan with the same number of VMs. Try to failover the new recovery plan instead of the stuck RP.

Will update the thread when we fix this issue.

Thank you,

Ruturaj

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

We are looking into this issue offline. There seems to be a bug in the service and we are looking at fixing it.

For all others , If you hit this issue, kindly create a new recovery plan with the same number of VMs. Try to failover the new recovery plan instead of the stuck RP.

Will update the thread when we fix this issue.

Thank you,

Ruturaj

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Tuesday, July 14, 2015 10:08 AM

We are looking into this issue offline. There seems to be a bug in the service and we are looking at fixing it.

For all others , If you hit this issue, kindly create a new recovery plan with the same number of VMs. Try to failover the new recovery plan instead of the stuck RP.

Will update the thread when we fix this issue.

Thank you,

Ruturaj

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Tuesday, July 14, 2015 10:08 AM

We are looking into this issue offline. There seems to be a bug in the service and we are looking at fixing it.

For all others , If you hit this issue, kindly create a new recovery plan with the same number of VMs. Try to failover the new recovery plan instead of the stuck RP.

Will update the thread when we fix this issue.

Thank you,

Ruturaj

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Tuesday, July 14, 2015 10:08 AM

We are looking into this issue offline. There seems to be a bug in the service and we are looking at fixing it.

For all others , If you hit this issue, kindly create a new recovery plan with the same number of VMs. Try to failover the new recovery plan instead of the stuck RP.

Will update the thread when we fix this issue.

Thank you,

Ruturaj

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Tuesday, July 14, 2015 10:08 AM

We are looking into this issue offline. There seems to be a bug in the service and we are looking at fixing it.

For all others , If you hit this issue, kindly create a new recovery plan with the same number of VMs. Try to failover the new recovery plan instead of the stuck RP.

Will update the thread when we fix this issue.

Thank you,

Ruturaj

• Marked as answer by Ruturaj DhekaneMicrosoft employee, Owner Tuesday, July 14, 2015 10:08 AM