question

devop228 avatar image
0 Votes"
devop228 asked Prrudram-MSFT commented

Resource Not Found while unregistering MARS server

Hi,

I'm trying to unregister a Azure VM server using MARS agent from a Recovery Services Vault. I used MARS management console to delete all backup items but still seeing the server listed under "Backup Infrastructure" -> "Azure Backup Agent". I went on and try to delete it from the portal, but got an error say "VM no longer exists". Due to this error, I couldn't delete the vault. Would anyone help me to resolve this issue, thanks.

198018-deletingserver.png

198082-error.png


azure-backup
deletingserver.png (18.6 KiB)
error.png (10.0 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Prrudram-MSFT avatar image
0 Votes"
Prrudram-MSFT answered Prrudram-MSFT commented

Hello @devop228,

Thank you for reaching out to the Microsoft Q&A platform. Happy to answer your question.

Error: Deletion failed

Error message: Could not perform the operation as VM no longer exists.

Resolution:

VM no longer exists. Stop protecting virtual machine without deleting backup data. More details refer this article

Please "Accept as Answer" and Upvote if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.



· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for the quick response.

I checked the Backup items of the vault, there is no backup item at all. Please see the attached screenshot below. Would you please give me more hints thanks.

198356-image.png


0 Votes 0 ·
image.png (17.4 KiB)

Hello @Devop228,

I think this ended up in leaving some stale entries in the backend that's what is blocking from unregistering this server from vault's backup infrastructure. Can you try to unregister the server using PowerShell approach documented here https://docs.microsoft.com/en-us/powershell/module/az.recoveryservices/unregister-azrecoveryservicesbackupcontainer?view=azps-7.5.0


Ex: $Cont = Get-AzRecoveryServicesBackupContainer -ContainerType "Windows" -BackupManagementType MAB -Name "server01.contoso.com"
Unregister-AzRecoveryServicesBackupContainer -Container $Cont

This once happened to me in a test scenario, and I used PS way which helped. Let me know how that goes for you.

0 Votes 0 ·

Hi @Prrudram-MSFT,

Thank you for the instructions. I tried the commands you suggested with some modifications without success. It still reported "The specified resource does not exist". Attached is the cmdlets I used. I'm happy to send you the subscriptionId if you need.


![198969-image.png][1]


0 Votes 0 ·
image.png (47.7 KiB)
devop228 avatar image
1 Vote"
devop228 answered Prrudram-MSFT commented

Hi,

With the help from @Prrudram-MSFT and Microsoft support, this issue was resolved. An bug was raised with reference ID 305895077.

The cause of the issue is quoted from Microsoft Support's email here for future reference and hopefully helps others with similar issue.

Cause Analysis
We have recently migrated our services to Service fabric from Cloud Service.

As part of this migration, one bug got introduced in one of our service (RRP service). Due to this bug request URI which is having dot (.) in machine name/ container name, is getting >modified and that dot is getting removed from container name while forwarding request to other service (BMS).

BMS service is responsible for fetching container and datasource details...due to wrong container name received from RRP, BMS is not able to fetch the data source and things are broken.

Solution
We have enabled traffic back to RDFE/cloud service and stopped service fabric traffic in AE geo.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@devop228 Thank you for posting the resolution for the benefit of community.

0 Votes 0 ·