|
| 1 | +--- |
| 2 | +title: Recover from accidental deletion of resource bridge VM |
| 3 | +description: Learn how to perform recovery operations for the Azure Arc resource bridge VM in Azure Arc-enabled System Center Virtual Machine Manager (preview) disaster scenarios. |
| 4 | +ms.topic: how-to |
| 5 | +ms.custom: |
| 6 | +ms.date: 07/28/2023 |
| 7 | +ms.services: azure-arc |
| 8 | +ms.subservice: azure-arc-scvmm |
| 9 | +author: jyothisuri |
| 10 | +ms.author: jsuri |
| 11 | +--- |
| 12 | + |
| 13 | +# Recover from accidental deletion of resource bridge virtual machine |
| 14 | + |
| 15 | +In this article, you'll learn how to recover the Azure Arc resource bridge (preview) connection into a working state in disaster scenarios such as accidental deletion. In such cases, the connection between on-premises infrastructure and Azure is lost and any operations performed through Arc will fail. |
| 16 | + |
| 17 | +## Recover the Arc resource bridge in case of virtual machine deletion |
| 18 | + |
| 19 | +To recover from Arc resource bridge VM deletion, you need to deploy a new resource bridge with the same resource ID as the current resource bridge using the following steps. |
| 20 | + |
| 21 | +1. Copy the Azure region and resource IDs of the Arc resource bridge, custom location, and SCVMM Azure resources. |
| 22 | + |
| 23 | +2. Find and delete the old Arc resource bridge template from your SCVMM. |
| 24 | + |
| 25 | +3. Download the [onboarding script](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#download-the-onboarding-script) from the Azure portal and update the following section in the script, using the same information as the original resources in Azure. |
| 26 | + |
| 27 | + ```powershell |
| 28 | + $location = <Azure region of the resources> |
| 29 | + $applianceSubscriptionId = <subscription-id> |
| 30 | + $applianceResourceGroupName = <resource-group-name> |
| 31 | + $applianceName = <resource-bridge-name> |
| 32 | +
|
| 33 | + $customLocationSubscriptionId = <subscription-id> |
| 34 | + $customLocationResourceGroupName = <resource-group-name> |
| 35 | + $customLocationName = <custom-location-name> |
| 36 | +
|
| 37 | + $vmmserverSubscriptionId = <subscription-id> |
| 38 | + $vmmserverResourceGroupName = <resource-group-name> |
| 39 | + $vmmserverName= <SCVMM-name-in-azure> |
| 40 | + ``` |
| 41 | +
|
| 42 | +4. [Run the onboarding script](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#download-the-onboarding-script) again with the `--force` parameter. |
| 43 | +
|
| 44 | + ``` powershell-interactive |
| 45 | + ./resource-bridge-onboarding-script.ps1 --force |
| 46 | + ``` |
| 47 | +
|
| 48 | +5. [Provide the inputs](/azure/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc#script-runtime) as prompted. |
| 49 | +
|
| 50 | +6. Once the script successfully finishes, the resource bridge should be recovered, and the previously disconnected Arc-enabled resources will be manageable in Azure again. |
| 51 | +
|
| 52 | +## Next steps |
| 53 | +
|
| 54 | +[Troubleshoot Azure Arc resource bridge (preview) issues](../resource-bridge/troubleshoot-resource-bridge.md) |
| 55 | +
|
| 56 | +If the recovery steps mentioned above are unsuccessful in restoring Arc resource bridge to its original state, try one of the following channels for support: |
| 57 | +
|
| 58 | +- Get answers from Azure experts through [Microsoft Q&A](/answers/topics/azure-arc.html). |
| 59 | +- Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience. Azure Support connects the Azure community to answers, support, and experts. |
| 60 | +- [Open an Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md). |
0 commit comments