Recovery Vault with legacy DPM Data. Unable to Remove or Delete

Alan Rudman (Tenant) 0 Reputation points
2026-08-10T15:48:59.4233333+00:00

I have a Recovery Services Vault that was used to store DPM backups. This was deprecated and has been unused for over a year now, but no matter what I do, I am unable to purge this data and remove the Vault and Resource Group. I have followed numerous threads on how to do this, but with no success.

I even rebuilt the old DPM server and reconnected it back to the vault to try removing it that way.

At this point, I am at a loss as to how to purge this data.

Thanks

Azure Site Recovery
Azure Site Recovery

An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-08-10T15:49:20.4233333+00:00

    This vault cannot be deleted until every dependency is removed. For legacy DPM data, the blocking items are usually one or more of these:

    1. Backup items still exist or are retained
      • In the vault, go to Backup Items.
      • Under Backup Management Type, select DPM or Azure Backup Server and inspect the protected data sources.
      • If protection was stopped but data was retained, the item can still appear in the vault and billing continues until the online recovery points are completely deleted.
    2. Delete the DPM-backed items from the DPM console In the DPM Administrator Console:
      • Go to Protection.
      • Select the protection group member.
      • Right-click Stop Protection of Group Members.
      • Select Delete protected data and Delete storage online.
      • Complete the operation.
      • For supported versions, generate the Security PIN in Azure portal from Recovery Services vault > Settings > Properties > Security PIN > Generate, then paste it into DPM.
      • If needed afterward, right-click the inactive protection group and select Remove inactive protection, then select Delete online storage.
      An alternate DPM method is to open the MABS management or DPM management console and, under Select data protection method, clear I want online protection.
    3. Then remove the DPM server registration from the vault In Azure portal:
      • Go to Recovery Services vault > Backup Infrastructure > Backup Management Servers.
      • Delete or unregister all DPM or MABS management servers.
      • Deleting MABS or DPM servers also removes the corresponding backup items protected in the vault.
    4. Check for soft-deleted backup data Even after deletion, backup data can block vault deletion while in soft-deleted state.
      • Go to Properties > Security Settings and disable Soft Delete if enabled.
      • If items are already soft-deleted, restore them and delete them again so they can be permanently deleted.
      • For MARS-managed deletions, the portal notes deleted backup data is retained for 14 days before permanent deletion. The vault cannot be deleted while soft-deleted items remain.
    5. Disable other vault protections that block deletion
      • If Multi-user authorization (MUA) is enabled, required authorization must be obtained before deletion.
      • In Properties > Security Settings, disable Security Features if enabled.
    6. Remove remaining infrastructure dependencies Check and clear all of these before retrying vault deletion:
      • Backup Infrastructure > Protected Servers
      • Backup Infrastructure > Backup Management Servers
      • Backup Infrastructure > Storage Accounts
      • Settings > Networking > Private access for any private endpoints
    7. Delete the vault Once Essentials shows no backup items, backup management servers, or replicated items:
      • Open the vault.
      • Select Delete.
      • Confirm deletion.
    8. If the vault is empty but still fails to delete Use one of the supported fallback methods:
      • From the vault Overview > Delete > Delete using PowerShell Script > Generate and Download Script. The generated script is customized for the vault and recursively deletes backup items, unregisters servers and storage accounts, removes private endpoints, and deletes the vault. This is destructive and cannot be undone.
      • If all dependencies are already removed and the portal still returns Vault deletion error, use the ARMClient method described for deleting the Recovery Services vault.
    9. If the DPM server is registered under the wrong backup management type There is a known case where deletion is blocked with the error that the same server is registered under a different Backup Management Type. That condition requires Microsoft support to correct from the backend.

    For the scenario described, the most likely end-to-end path is:

    1. In Backup Items, verify whether legacy DPM data sources still appear under DPM or Azure Backup Server.
    2. In the rebuilt DPM server, use Stop Protection of Group Members with Delete protected data and Delete storage online.
    3. In the vault, remove the DPM management server from Backup Infrastructure > Backup Management Servers.
    4. Disable Soft Delete and clear any soft-deleted items.
    5. Remove storage accounts and private endpoints if present.
    6. Retry vault deletion.
    7. If the vault is empty and still blocked, run the generated vault-deletion PowerShell script or use ARMClient.
    8. If the error specifically mentions registration under a different backup management type, backend support is required.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.