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/energy-data-services/how-to-manage-upgrade-settings.md
+11-22Lines changed: 11 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,8 +24,8 @@ Azure Data Manager for Energy provides two upgrade policy options:
24
24
25
25
| Policy | Description |
26
26
|--------|-------------|
27
-
|**Automatic**|Your instance is automatically upgraded when a new milestone release is available. This option is the default setting for all instances. |
28
-
|**Deferred**|Your instance upgrade is deferred, giving you up to 30 days to validate the new milestone release before your instance is upgraded. |
27
+
|**Automatic**|Instance is upgraded automatically when a new milestone release is available. This option is the default setting for all instances. |
28
+
|**Deferred**|Upgrades are deferred for up to 30 days before instance is upgraded. |
29
29
30
30
If you have multiple Azure Data Manager for Energy instances, you can set different upgrade policies for each one. For example, you might set one instance to **Automatic** so it upgrades immediately when a new milestone is released, allowing you to test and validate the changes. Meanwhile, you can set your production instance to **Deferred** to delay the upgrade until you complete your testing. At any point during the 30-day window, you can mark your deferred instance as ready for upgrade. If you don't take action, the instance is automatically upgraded at the end of the 30-day window.
31
31
@@ -35,27 +35,20 @@ If you have multiple Azure Data Manager for Energy instances, you can set differ
35
35
36
36
1. In the left menu under **Advanced**, select **Upgrade Settings**.
37
37
38
-
ADD SCREENSHOT HERE
39
-
40
38
1. On the **Upgrade Settings** page, you can view:
41
-
-**Current milestone version**: The current milestone version your instance is running (for example, M25 or M26).
42
39
-**Upgrade policy**: Whether your instance is set to **Automatic** or **Deferred** upgrades.
43
-
-**Auto upgrade after date**: If your upgrade policy is set to **Deferred** and a milestone upgrade is available, this field shows the date when your instance is automatically upgraded.
44
-
45
-
ADD SCREENSHOT HERE
40
+
-**Automatic upgrade after**: If your upgrade policy is set to **Deferred** and a milestone upgrade is available, this field shows the date when your instance is automatically upgraded.
46
41
47
42
> [!NOTE]
48
-
> The current milestone version is also displayed on the **Overview** page for your Azure Data Manager for Energy instance.
43
+
> The current milestone version is displayed in the **Essentials** section on the **Overview** page for your Azure Data Manager for Energy instance.
49
44
50
45
## Configure upgrade settings during instance creation
51
46
52
47
You can configure upgrade settings when you create a new Azure Data Manager for Energy instance.
53
48
54
49
1. When creating a new instance, navigate to the **Advanced Settings** tab.
55
50
56
-
1. In the **Upgrade Settings** section, you can choose to enable **Defer Milestone Upgrades**.
57
-
58
-
ADD SCREENSHOT HERE
51
+
1. In the **Upgrade Settings** section, select either **Automatic** or **Deferred** for the **Upgrade Policy**.
59
52
60
53
1. Complete the remaining tabs and select **Create** to create your instance with the configured upgrade settings.
61
54
@@ -69,8 +62,6 @@ You can change the upgrade policy for an existing Azure Data Manager for Energy
69
62
70
63
1. Select either **Automatic** or **Deferred** to change your upgrade policy.
71
64
72
-
ADD SCREENSHOT HERE
73
-
74
65
1. Select **Save** to apply your changes.
75
66
76
67
## Mark your instance as ready for upgrade
@@ -81,14 +72,12 @@ If your upgrade policy is set to **Deferred** and a milestone upgrade is availab
81
72
82
73
1. In the left menu under **Advanced**, select **Upgrade Settings**.
83
74
84
-
1. Select the **Mark Ready for Milestone Upgrade** button.
85
-
86
-
ADD SCREENSHOT HERE
75
+
1. Select the **Mark Ready for Upgrade** button.
87
76
88
77
> [!NOTE]
89
-
> The **Mark Ready for Milestone Upgrade** button is only available when:
78
+
> The **Mark Ready for Upgrade** button is only available when:
90
79
> - Your upgrade policy is set to **Deferred**.
91
-
> -A milestone upgrade is available (the **30-Day Window End Date** is set).
80
+
> -The **Automatic upgrade after** date is set by the Azure Data Manager for Energy team.
92
81
93
82
1. Confirm that you want to mark your instance as ready for upgrade.
94
83
@@ -99,16 +88,16 @@ If your upgrade policy is set to **Deferred** and a milestone upgrade is availab
99
88
100
89
When a new milestone release is available and your upgrade policy is set to **Deferred**, the following apply:
101
90
102
-
1. After all instances with the **Automatic** upgrade policy are upgraded, the Azure Data Manager for Energy team sets the **30-Day Window End Date**, which is approximately 30 days from that point.
91
+
1. After all instances with the **Automatic** upgrade policy are upgraded, the Azure Data Manager for Energy team sets the **Automatic upgrade after** date, which is approximately 30 days from that point.
103
92
104
-
1. The **30-Day Window End Date** is displayed on the **Upgrade Settings** page in the Azure portal.
93
+
1. The **Automatic upgrade after**date is displayed on the **Upgrade Settings** page in the Azure portal for instances with a **Deferred** upgrade policy.
105
94
106
95
1. During this 30-day window, you can:
107
96
- Test the new milestone release in a nonproduction environment.
108
97
- Mark your instance as ready for upgrade when you're satisfied with your testing.
109
98
- Take no action and let your instance be automatically upgraded at the end of the window.
110
99
111
-
1. After your instance is upgraded, the **30-Day Window End Date** is cleared until the next milestone release.
100
+
1. After your instance is upgraded, the **Automatic upgrade after** date is cleared until the next milestone release.
0 commit comments