Skip to content

Commit b5f6f5f

Browse files
committed
Minor updates
1 parent c70b8e4 commit b5f6f5f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-arc/system-center-virtual-machine-manager/disaster-recovery.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ If you had deployed Arc Resource Bridge earlier using DHCP, you must clean up yo
3434
2. Download [this script](https://download.microsoft.com/download/a/a/8/aa8687e4-1a30-485f-9de4-4f15fc576724/resource-bridge-onboarding-script-dr.ps1) and update the following section in the script using the same information as the original resources in Azure.
3535

3636
```powershell
37-
$location = <Azure region of the resources>
37+
$location = <Azure region of the original Arc resource bridge>
3838
$applianceSubscriptionId = <subscription-id>
3939
$applianceResourceGroupName = <resource-group-name>
4040
$applianceName = <resource-bridge-name>
@@ -48,7 +48,7 @@ If you had deployed Arc Resource Bridge earlier using DHCP, you must clean up yo
4848
$vmmserverName= <SCVMM-name-in-azure>
4949
```
5050

51-
3. [Provide the inputs](quickstart-connect-system-center-virtual-machine-manager-to-arc.md#script-runtime) as prompted.
51+
3. Run the updated script from the same location where the config YAML files are stored after the initial onboarding. This is most likely the same folder from where you ran the initial onboarding script unless the config files were moved later to a different location. [Provide the inputs](quickstart-connect-system-center-virtual-machine-manager-to-arc.md#script-runtime) as prompted.
5252

5353
4. Once the script is run successfully, the old Resource Bridge is recovered, and the connection is re-established to the existing Azure-enabled SCVMM resources.
5454

0 commit comments

Comments
 (0)