You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/devtest-labs/how-to-move-schedule-to-new-region.md
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,15 +39,18 @@ To get started, you'll export and modify a Resource Manager template that contai
39
39
40
40
1. Move your current DevTest Lab to the new region and resource group by using the steps included in the article, [Move a DevTest Labs to another region](./how-to-move-labs.md).
41
41
42
-
1. Optionally, you can move your current Virtual Network to the new region and resource group by using the steps included in the article, [Move an Azure virtual network to another region](../virtual-network/move-across-regions-vnet-portal.md).
42
+
1. Optionally, move your current virtual network to the new region and resource group by using the steps included in the article, [Move an Azure virtual network to another region](../virtual-network/move-across-regions-vnet-portal.md).
43
43
44
44
Alternately, you can create a new virtual network, if you don't have to keep the original one.
45
45
46
-
1. Move your Virtual Machines to the new region by using the steps included in the article, [Tutorial: Move Azure VMs across regions](../resource-mover/tutorial-move-region-virtual-machines.md).
46
+
1. Move your virtual machines to the new region by using the steps included in the article, [Tutorial: Move Azure VMs across regions](../resource-mover/tutorial-move-region-virtual-machines.md).
47
47
48
48
49
49
## Move the schedule
50
-
There are two ways to move a lab schedule. You can recreate any schedules you want to move on the moved VMs. This manual process can be time consuming, so it's most useful when you have a few schedules and VMs.
50
+
There are two ways to move a lab schedule:
51
+
52
+
- Manually recreate the schedules on the moved VMs. This process can be time consuming and error prone. This approach is most useful when you have a few schedules and VMs.
53
+
- Export and redeploy the schedules by using ARM templates.
51
54
52
55
Alternately, you can move your existing schedules by using the following steps:
53
56
@@ -60,7 +63,7 @@ Alternately, you can move your existing schedules by using the following steps:
60
63
(2) Select all resources with the type **Microsoft.DevTestLab/Schedules**<br>
61
64
(3) Select **Export template**<br>
62
65
63
-
:::image type="content" source="./media/how-to-move-schedule-to-new-region/move-compute-schedule.png" alt-text="Screenshot that shows the hidden resources in a resource group, with schedules selected.":::
66
+
:::image type="content" source="./media/how-to-move-schedule-to-new-region/move-compute-schedule.png" alt-text="Screenshot that shows the hidden resources in a resource group, with schedules selected.":::
64
67
65
68
5. On the **Export resource group template** page, select **Deploy**.
66
69
@@ -78,7 +81,7 @@ Alternately, you can move your existing schedules by using the following steps:
78
81
|**Schedule Name**|Must be a different name. |
79
82
|**VirtualMachine_xxx_externalId**|Must be the moved one, or the new one you just created. |
80
83
81
-
:::image type="content" source="./media/how-to-move-schedule-to-new-region/move-schedule-custom-deployment.png" alt-text="Screenshot that shows the custom deployment page, with new location values for the relevant settings.":::
84
+
:::image type="content" source="./media/how-to-move-schedule-to-new-region/move-schedule-custom-deployment.png" alt-text="Screenshot that shows the custom deployment page, with new location values for the relevant settings.":::
82
85
83
86
>[!IMPORTANT]
84
87
>Each schedule must have a globally unique name, so remember to change the schedule name for the new location.
@@ -95,6 +98,6 @@ Now you can choose to clean up the original schedules if they're longer used. Go
95
98
96
99
In this article, you moved a DevTest Labs schedule from one region to another and cleaned up the source resources. To learn more about moving resources between regions and disaster recovery in Azure, refer to:
97
100
98
-
-[Move a DevTest Labs to another region](./how-to-move-labs)
99
-
-[Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md)
100
-
-[Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md)
101
+
-[Move a DevTest Labs to another region](./how-to-move-labs).
102
+
-[Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md).
103
+
-[Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md).
0 commit comments