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
This article provides step-by-step procedure to perform point-in-time recoveries in flexible server using backups.
17
+
This article provides step-by-step procedure to perform point-in-time recoveries in Azure Database for MySQL flexible server using backups.
18
18
19
19
## Prerequisites
20
20
@@ -29,14 +29,14 @@ This article provides step-by-step procedure to perform point-in-time recoveries
29
29
az login
30
30
````
31
31
32
-
- If you have multiple subscriptions, choose the appropriate subscription in which you want to create the server using the ```az account set``` command.
32
+
- If you have multiple subscriptions, choose the appropriate subscription in which you want to create the server using the `az account set` command.
33
33
`
34
34
35
35
```azurecli
36
36
az account set --subscription <subscription id>
37
37
```
38
38
39
-
- Create a MySQL Flexible Server if you have not already created one using the ```az mysql flexible-server create``` command.
39
+
- Create an Azure Database for MySQL flexible server instance if you haven't already created one by using the `az mysql flexible-server create` command.
40
40
41
41
```azurecli
42
42
az mysql flexible-server create --resource-group myresourcegroup --name myservername
@@ -88,7 +88,7 @@ az mysql flexible-server geo-restore --source-server
88
88
```
89
89
90
90
**Example:**
91
-
Geo-restore 'mydemoserver' in region East US to a new server 'mydemoserver-restored' in it’s geo-paired location West US with the same network setting.
91
+
Geo-restore 'mydemoserver' in region East US to a new server 'mydemoserver-restored' in its geo-paired location West US with the same network setting.
92
92
93
93
```azurecli
94
94
az mysql flexible-server geo-restore \
@@ -102,10 +102,10 @@ az mysql flexible-server geo-restore \
102
102
103
103
After the restore is completed, you should perform the following tasks to get your users and applications back up and running:
104
104
105
-
- If the new server is meant to replace the original server, redirect clients and client applications to the new server
105
+
- If the new server is meant to replace the original server, redirect clients and client applications to the new server.
106
106
- Ensure appropriate VNet rules are in place for users to connect. These rules are not copied over from the original server.
107
-
- Ensure appropriate logins and database level permissions are in place
108
-
- Configure alerts as appropriate for the newly restore server
107
+
- Ensure appropriate logins and database level permissions are in place.
108
+
- Configure alerts as appropriate for the newly restore server.
This article provides step-by-step procedure to perform point-in-time recoveries in flexible server using backups.
17
+
This article provides step-by-step procedure to perform point-in-time recoveries in Azure Database for MySQL flexible server using backups.
18
18
19
19
## Prerequisites
20
20
21
21
To complete this how-to guide, you need:
22
22
23
-
- You must have anAzure Database for MySQL - Flexible Server.
23
+
- You must have anAzure Database for MySQL flexible server instance.
24
24
25
25
## Restore to the latest restore point
26
26
27
-
Follow these steps to restore your flexible server using an earliest existing backup.
27
+
Follow these steps to restore your Azure Database for MySQL flexible server instance using an earliest existing backup.
28
28
29
-
1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.
29
+
1. In the [Azure portal](https://portal.azure.com/), choose your Azure Database for MySQL flexible server instance that you want to restore the backup from.
30
30
31
31
1. Select **Overview** from the left panel.
32
32
@@ -46,9 +46,9 @@ Follow these steps to restore your flexible server using an earliest existing ba
46
46
47
47
## Restore to a fastest restore point
48
48
49
-
Follow these steps to restore your flexible server using an existing full backup as the fastest restore point.
49
+
Follow these steps to restore your Azure Database for MySQL flexible server instance using an existing full backup as the fastest restore point.
50
50
51
-
1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.
51
+
1. In the [Azure portal](https://portal.azure.com/), choose your Azure Database for MySQL flexible server instance that you want to restore the backup from.
52
52
53
53
1. Select **Overview** from the left panel.
54
54
@@ -70,9 +70,9 @@ Follow these steps to restore your flexible server using an existing full backup
70
70
71
71
## Restore from a full backup through the Backup and Restore page
72
72
73
-
Follow these steps to restore your flexible server using an existing full backup.
73
+
Follow these steps to restore your Azure Database for MySQL flexible server instance using an existing full backup.
74
74
75
-
1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.
75
+
1. In the [Azure portal](https://portal.azure.com/), choose your Azure Database for MySQL flexible server instance that you want to restore the backup from.
76
76
77
77
1. Select **Backup and Restore** from the left panel.
78
78
@@ -92,7 +92,7 @@ Follow these steps to restore your flexible server using an existing full backup
92
92
93
93
## Geo restore to latest restore point
94
94
95
-
1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.
95
+
1. In the [Azure portal](https://portal.azure.com/), choose your Azure Database for MySQL flexible server instance that you want to restore the backup from.
96
96
97
97
1. Select **Overview** from the left panel.
98
98
@@ -123,9 +123,9 @@ The new server created by geo restore has the same server admin sign-in name and
123
123
124
124
## Use restore to move a server from Public access to Private access
125
125
126
-
Follow these steps to restore your flexible server using an earliest existing backup.
126
+
Follow these steps to restore your Azure Database for MySQL flexible server instance using an earliest existing backup.
127
127
128
-
1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.
128
+
1. In the [Azure portal](https://portal.azure.com/), choose your Azure Database for MySQL flexible server instance that you want to restore the backup from.
129
129
130
130
1. From the overview page, select **Restore**.
131
131
@@ -142,18 +142,18 @@ Follow these steps to restore your flexible server using an earliest existing ba
142
142
1. In the **Connectivity method**, select **Private access (VNet Integration)**. Go to **Virtual Network** section, you can either select an already existing *virtual network* and *Subnet* that is delegated to *Microsoft.DBforMySQL/flexibleServers* or Create a new one by selecting the *create virtual network* link.
143
143
> [!NOTE]
144
144
> Only virtual networks and subnets in the same region and subscription is listed in the dropdown list. </br>
145
-
> The chosen subnet is delegated to *Microsoft.DBforMySQL/flexibleServers*. It means that only Azure Database for MySQL - Flexible Servers can use that subnet.</br>
145
+
> The chosen subnet is delegated to *Microsoft.DBforMySQL/flexibleServers*. It means that only Azure Database for MySQL flexible server instances can use that subnet.</br>
146
146
147
147
:::image type="content" source="./media/how-to-manage-virtual-network-portal/vnet-creation.png" alt-text="Screenshot of Vnet configuration." lightbox="./media/how-to-manage-virtual-network-portal/vnet-creation.png":::
148
148
149
149
1. Create a new or Select an existing **Private DNS Zone**.
150
150
> [!NOTE]
151
151
> Private DNS zone names must end with `mysql.database.azure.com`. </br>
152
-
> If you do not see the option to create a new private dns zone, please enter the server name on the **Basics** tab.</br>
153
-
> After the flexible server is deployed to a virtual network and subnet, you cannot move it to Public access (allowed IP addresses).</br>
152
+
> If you don't see the option to create a new private dns zone, enter the server name on the **Basics** tab.</br>
153
+
> After the Azure Database for MySQL flexible server instance is deployed to a virtual network and subnet, you can't move it to Public access (allowed IP addresses).</br>
154
154
155
155
:::image type="content" source="./media/how-to-manage-virtual-network-portal/private-dns-zone.png" alt-text="Screenshot of dns configuration." lightbox="./media/how-to-manage-virtual-network-portal/private-dns-zone.png":::
156
-
1. Select **Review + create** to review your flexible server configuration.
156
+
1. Select **Review + create** to review your Azure Database for MySQL flexible server configuration.
157
157
1. Select **Create** to provision the server. Provisioning can take a few minutes.
158
158
159
159
1. A notification is shown that the restore operation has been initiated.
@@ -165,7 +165,7 @@ After the restore is completed, you should perform the following tasks to get yo
165
165
- If the new server is meant to replace the original server, redirect clients and client applications to the new server.
166
166
- Ensure appropriate virtual network rules are in place for users to connect. These rules aren't copied over from the original server.
167
167
- Ensure appropriate logins and database level permissions are in place.
168
-
- Configure alerts as appropriate for the newly restore server.
168
+
- Configure alerts as appropriate for the newly restored server.
You can use server logs to help monitor and troubleshoot an instance of Azure Database for MySQL - Flexible Server, and to gain detailed insights into the activities that have run on your servers.
16
-
By default, the server logs feature in Azure Database for MySQL - Flexible Server is disabled. However, after you enable the feature, a flexible server starts capturing events of the selected log type and writes them to a file. You can then use the Azure portal or the Azure CLI to download the files to assist with your troubleshooting efforts.
17
-
This article explains how to enable the server logs feature in Azure Database for MySQL - Flexible Server and download server log files. It also provides information about how to disable the feature.
15
+
You can use server logs to help monitor and troubleshoot an instance of Azure Database for MySQL flexible server, and to gain detailed insights into the activities that have run on your servers.
16
+
By default, the server logs feature in Azure Database for MySQL flexible server is disabled. However, after you enable the feature, an Azure Database for MySQL flexible server instance starts capturing events of the selected log type and writes them to a file. You can then use the Azure portal or the Azure CLI to download the files to assist with your troubleshooting efforts.
17
+
This article explains how to enable the server logs feature in Azure Database for MySQL flexible server and download server log files. It also provides information about how to disable the feature.
18
18
19
19
In this tutorial, you’ll learn how to:
20
20
- Enable the server logs feature.
@@ -23,17 +23,17 @@ In this tutorial, you’ll learn how to:
23
23
24
24
## Prerequisites
25
25
26
-
To complete this tutorial, you need an existing Azure Database for MySQL - Flexible Server. If you need to create a new server, see [Create an Azure Database for MySQL - Flexible Server](./quickstart-create-server-portal.md).
26
+
To complete this tutorial, you need an existing Azure Database for MySQL flexible server instance. If you need to create a new server, see [Create an Azure Database for MySQL flexible server instance](./quickstart-create-server-portal.md).
27
27
28
28
## Enable Server logs
29
29
30
30
To enable the server logs feature, perform the following steps.
31
31
32
-
1. In the [Azure portal](https://portal.azure.com), select your MySQL flexible server.
32
+
1. In the [Azure portal](https://portal.azure.com), select your Azure Database for MySQL flexible server instance.
33
33
34
34
2. On the left pane, under **Monitoring**, select **Server logs**.
35
35
36
-
:::image type="content" source="./media/how-to-server-logs-portal/1-how-to-serverlog.png" alt-text="Screenshot showing Azure Database for My SQL - Server Logs.":::
36
+
:::image type="content" source="./media/how-to-server-logs-portal/1-how-to-serverlog.png" alt-text="Screenshot showing Azure Database for MySQL flexible server Server Logs.":::
37
37
38
38
3. To enable server logs, under **Server logs**, select **Enable**.
39
39
@@ -47,7 +47,7 @@ To enable the server logs feature, perform the following steps.
To configure slow_logs on your Azure Database for MySQL - Flexible Server, see [Query Performance Insight.](./tutorial-query-performance-insights.md)
50
+
To configure slow_logs on your Azure Database for MySQL flexible server instance, see [Query Performance Insight.](./tutorial-query-performance-insights.md)
51
51
52
52
53
53
## Download Server logs
@@ -60,7 +60,7 @@ To download server logs, perform the following steps.
60
60
61
61
:::image type="content" source="./media/how-to-server-logs-portal/4-how-to-serverlog.png" alt-text="Screenshot showing Server Logs - Download.":::
62
62
63
-
For HA enabled Azure Database for MySQL - Flexible Server, server logs for standby server can be identified by another four-letter identifier after the hostname of the server as shown below.
63
+
For HA enabled Azure Database for MySQL flexible server instances, server logs for standby server can be identified by another four-letter identifier after the hostname of the server as shown below.
64
64
65
65
:::image type="content" source="./media/how-to-server-logs-portal/5-how-to-serverlog.png" alt-text="Screenshot showing server Logs - HA logs.":::
0 commit comments