Disabled Azure Site Recovery stuck, can't create another one

Question

Disabled Azure Site Recovery stuck, can't create another one

Steve Downey 5

I had Azure Site Recovery working fine for a VM, but I needed to change the tier of the source VM hard drive, so for replication to work after I had to disable it and intend to enable it again, but it's struck on "You cannot modify any settings as replicated item current state doesn't allow it." for 2 days and I can't get rid of it.

What can i do?

In the site recovery vault this VM isn't listed anymore under replications.

3 answers

Your answer

Answer 1

If you're experiencing issues with Azure Site Recovery being stuck and unable to modify settings for your VM, here are some steps you can take to resolve the problem:

Check for Resource Locks: Ensure that there are no resource locks on the VM or the resource group. If there are locks, they need to be removed before you can modify the settings.
Remove Stale Configuration: If the VM isn't listed under replications in the Site Recovery vault, it might be due to stale configurations. You can use the script to remove stale Site Recovery configurations. Download the script from the provided GitHub link and run it with the appropriate parameters (Subscription ID, VM Resource Group, and VM name).
Wait for Cleanup Jobs: Sometimes, Azure may take time to complete background cleanup jobs. If you have recently disabled replication, it may still be processing. You can check the Azure portal for any ongoing jobs related to the VM.
Contact Azure Support: If the above steps do not resolve the issue, consider reaching out to Azure Support for further assistance, as they can provide more detailed insights into your specific situation.

By following these steps, you should be able to troubleshoot and resolve the issue with Azure Site Recovery for your VM.

References:

Steve Downey 5 Reputation points

2025-12-02T16:57:35.7033333+00:00

I ran "the script from the provided GitHub link" and have the AZ module installed in Powershell but getting errors "the term Login-AzAccount is not recognized as the name of a cmdlet", same with all the other Az cmdlet calls

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

Bharath Y P 2,560 Microsoft External Staff Moderator

Hello Steve Downey,

It looks like you're having trouble with Azure Site Recovery after modifying the VM's hard drive tier. That can be frustrating! Here are some steps you can try to resolve the issue:

Check the Status: Make sure the Azure Site Recovery replication job isn't running or stuck. Go to the Azure portal, navigate to your Recovery Services vault, and check under "Site Recovery Jobs" for any ongoing jobs related to your VM.
Retry Disabling Replication: Sometimes, the Azure portal may take time to reflect changes. You can try to disable the replication again for the VM. Go to the "Replicated Items" in your Recovery Services vault, find the VM, and click on "Stop Replication." If it's unresponsive, wait a few more hours and try again.
PowerShell Command: If the above steps don't work, you might need to use PowerShell to forcefully disable replication. You can use the Stop-AzSiteRecoveryProtection cmdlet. Here's a basic example:
```
   Stop-AzSiteRecoveryProtection -ResourceGroupName "YourResourceGroup" -VaultName "YourVaultName" -Name "YourVMName" -Force
```
Make sure to replace the placeholders with your actual resource group, vault name, and VM name.
Re-enable Replication: Once the replication has been successfully stopped, you should be able to set it up again by following the usual process in the UI or via PowerShell.

I hope this helps you get unstuck! Let me know if you have further questions.

Reference documents :

Azure Site Recovery Documentation : [Site Recovery](https://learn.microsoft.com/en-us/azure Site Recovery/)
PowerShell Cmdlet for Azure Site Recovery: Stop-AzSiteRecoveryProtection

Hope this helps, if you need further assistance. Feel free to reach out to us, thanks.

Steve Downey 5 Reputation points

2025-12-03T09:38:23.9+00:00

Thanks for the answer but there are no running jobs, the VM isn't there in replicated items anymore and in Powershell I get the error "The term 'Stop-AzSiteRecoveryProtection' is not recognized as a name of a cmdlet" even though I have the AZ module loaded
Steve Downey 5 Reputation points

2025-12-03T10:14:21.36+00:00

I'm trying to run do through Get-AzRecoveryServicesVault and Set-AzRecoveryServicesAsrVaultContext, but the latter produces "Object reference not set to an instance of an object".
Hitting brick walls with this and don't know what to do, your second link goes to a 404 page and the first is just the Microsoft learn home page so no help.
Steve Downey 5 Reputation points

2025-12-05T11:24:08.1666667+00:00

Can nobody help me? Replication has been stuck now for nearly a week this is very bad, no suggested solution works
Bharath Y P 2,560 Reputation points Microsoft External Staff Moderator

2025-12-05T17:17:07.8633333+00:00
Hello Steve Downey, Thanks for the update. Apologies for the above response, The Stop-AzSiteRecoveryProtection and Set-AzRecoveryServicesAsrVaultContext commands are from the old AzureRM Site Recovery module. They don’t exist in the modern Az.RecoveryServices module, which is why you’re seeing “not recognized” and “Object reference not set…” errors.

The vault thinks the VM is still protected, but the portal doesn’t list it. That’s why you’re blocked from re‑enabling replication.

Here’s the sequence that works with the current Az cmdlets:

# Make sure you have the latest Az.RecoveryServices module Install-Module -Name Az.RecoveryServices -Force Import-Module Az.RecoveryServices # 1. Get your vault $vault = Get-AzRecoveryServicesVault -Name "YourVaultName" -ResourceGroupName "YourResourceGroup" # 2. Set vault context (this is the correct cmdlet) Set-AzRecoveryServicesVaultContext -Vault $vault # 3. List protection containers Get-AzRecoveryServicesAsrProtectionContainer # 4. List replication protected items Get-AzRecoveryServicesAsrReplicationProtectedItem # 5. If your VM still appears, force remove it Remove-AzRecoveryServicesAsrReplicationProtectedItem ` -ReplicationProtectedItem <ID> ` -ProtectionContainer <ContainerID> ` -Force

If the VM Doesn’t Show Up:

Check VM extensions: In the Azure portal > VM > Extensions + applications. If the SiteRecovery (Mobility Service) extension is still installed, remove it manually.

Check vault infrastructure: In the Vault > Site Recovery Infrastructure > Configuration Servers. Refresh the server; sometimes the VM shows up under “Not protected” and can be removed there.

If neither PowerShell nor portal shows the VM, the backend record is orphaned. At that point, only Microsoft support can purge it.

Share via

Disabled Azure Site Recovery stuck, can't create another one

3 answers

Your answer