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/migrate/troubleshoot-assessment.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ The operation took longer than expected either due to network latency issues or
68
68
69
69
- Ensure that there is no network latency between the appliance and the server. It is recommended to have the appliance and source server on the same domain to avoid latency issues.
70
70
71
-
- Connect to the impacted server from the appliance and run the commands documented here to check if they return null or empty data.
71
+
- Connect to the impacted server from the appliance and run the commands documented [here](discovered-metadata.md#linux-server-metadata) to check if they return null or empty data.
72
72
73
73
- If the issue persists, submit a Microsoft support case providing the appliance machine ID (available in the footer of the appliance configuration manager).
74
74
@@ -203,7 +203,7 @@ The error details will be mentioned with the error.
203
203
204
204
#### Recommended Action
205
205
206
-
Ensure that port 443 is open on the ESXi host on which the server is running. Learn more on how to remediate the issue.
206
+
Ensure that port 443 is open on the ESXi host on which the server is running. [Learn more](troubleshoot-discovery.md#error-9014-httpgetrequesttoretrievefilefailed) on how to remediate the issue.
207
207
208
208
### Error Code: 9015: The vCenter Server user account provided for server discovery doesn't have guest operations privileges enabled.
209
209
@@ -213,7 +213,7 @@ The required privileges of guest operations haven't been enabled on the vCenter
213
213
214
214
#### Recommended Action
215
215
216
-
Ensure that the vCenter Server user account has privileges enabled for **Virtual Machines** > **Guest Operations** to interact with the server and pull the required data. Learn more on how to set up the vCenter Server account with required privileges.
216
+
Ensure that the vCenter Server user account has privileges enabled for **Virtual Machines** > **Guest Operations** to interact with the server and pull the required data. [Learn more](./vmware/tutorial-discover-vmware.md#create-an-account-to-access-vcenter-server) on how to set up the vCenter Server account with required privileges.
217
217
218
218
### Error Code: 9022: The access is denied to run the Get-WmiObject cmdlet on the server.
Copy file name to clipboardExpand all lines: articles/mysql/flexible-server/concepts-maintenance.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,10 @@ You can define system-managed schedule or custom schedule for each flexible serv
53
53
* With system-managed schedule, the system will pick any one-hour window between 11pm and 7am in your server's region time.
54
54
55
55
> [!IMPORTANT]
56
-
> Previously, a 7-day deployment gap between system-managed and custom-managed schedules was maintained. Due to evolving maintenance demands and the introduction of the [maintenance reschedule feature (Public preview)](#maintenance-reschedule-public-preview), we can no longer guarantee this 7-day gap.
56
+
> Starting from 31st August 2024, Azure Database for MySQL will no longer support custom maintenance windows for burstable SKU instances. This change is due to the need for simplifying maintenance processes, ensuring optimal performance, and our analysis indicating that the number of users utilizing custom maintenance windows on burstable SKUs is minimal. Existing burstable SKU instances with custom maintenance window configurations will remain unaffected; however, users will not be able to modify these custom maintenance window settings moving forward.
57
+
>
58
+
> For customers requiring custom maintenance windows, we recommend upgrading to General Purpose or Business Critical SKUs to continue using this feature.
59
+
57
60
58
61
59
62
In rare cases, maintenance event can be canceled by the system or may fail to complete successfully. If the update fails, the update is reverted, and the previous version of the binaries is restored. In such failed update scenarios, you may still experience restart of the server during the maintenance window. If the update is canceled or failed, the system will create a notification about canceled or failed maintenance event respectively notifying you. The next attempt to perform maintenance will be scheduled as per your current scheduling settings and you will receive notification about it 5 days in advance.
16.04 LTS | [9.57](https://support.microsoft.com/topic/e94901f6-7624-4bb4-8d43-12483d2e1d50) | No new 16.04 LTS kernels supported in this release. |
172
172
16.04 LTS | [9.56](https://support.microsoft.com/topic/update-rollup-69-for-azure-site-recovery-kb5033791-a41c2400-0079-4f93-b4a4-366660d0a30d) | No new 16.04 LTS kernels supported in this release. |
173
173
|||
174
-
18.04 LTS | 9.62| No new 18.04 LTS kernels supported in this release. |
18.04 LTS | [9.57](https://support.microsoft.com/topic/e94901f6-7624-4bb4-8d43-12483d2e1d50) | No new 18.04 LTS kernels supported in this release. |
178
178
18.04 LTS | [9.56](https://support.microsoft.com/topic/update-rollup-69-for-azure-site-recovery-kb5033791-a41c2400-0079-4f93-b4a4-366660d0a30d) | No new 18.04 LTS kernels supported in this release. |
179
179
|||
180
-
20.04 LTS | 9.62| No new 20.04 LTS kernels supported in this release. |
@@ -219,7 +219,7 @@ Debian 9.1 | [9.60]| No new Debian 9.1 kernels supported in this release. |
219
219
Debian 9.1 | [9.57](https://support.microsoft.com/topic/e94901f6-7624-4bb4-8d43-12483d2e1d50)| No new Debian 9.1 kernels supported in this release. |
220
220
Debian 9.1 | [9.56](https://support.microsoft.com/topic/update-rollup-69-for-azure-site-recovery-kb5033791-a41c2400-0079-4f93-b4a4-366660d0a30d)| No new Debian 9.1 kernels supported in this release. |
221
221
|||
222
-
Debian 10 | 9.62| No new Debian 10 kernels supported in this release. |
0 commit comments