Skip to content

Commit

Permalink
Merge pull request #6 from markingmyname/246057
Browse files Browse the repository at this point in the history
[MySQL] Added new images and edited alt text.
  • Loading branch information
VandhanaMehta authored Aug 23, 2023
2 parents 1718303 + 679bf78 commit 556bb1d
Show file tree
Hide file tree
Showing 4 changed files with 72 additions and 74 deletions.
146 changes: 72 additions & 74 deletions articles/mysql/flexible-server/how-to-restore-server-portal.md
Original file line number Diff line number Diff line change
@@ -1,17 +1,19 @@
---
title: Restore an Azure Database for MySQL - Flexible Server with Azure portal.
title: Restore MySQL - Flexible Server with Azure portal
titleSuffix: Azure Database for MySQL - Flexible Server
description: This article describes how to perform restore operations in Azure Database for MySQL - Flexible Server through the Azure portal
author: code-sidd
ms.author: sisawant
ms.reviewer: maghan
ms.date: 08/22/2023
ms.service: mysql
ms.subservice: flexible-server
ms.topic: how-to
author: code-sidd
ms.author: sisawant
ms.date: 07/26/2022
---

# Point-in-time restore of a Azure Database for MySQL - Flexible Server using Azure portal
# Point-in-time restore of an Azure Database for MySQL - Flexible Server using Azure portal

[!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
[!INCLUDE [applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]

This article provides step-by-step procedure to perform point-in-time recoveries in flexible server using backups.

Expand All @@ -27,147 +29,143 @@ Follow these steps to restore your flexible server using an earliest existing ba

1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.

2. Click **Overview** from the left panel.
1. Select **Overview** from the left panel.

3. From the overview page, click **Restore**.
1. From the overview page, select **Restore**.

4. Restore page will be shown with an option to choose between **Latest restore point** and Custom restore point.
1. Restore page is shown with an option to choose between **Latest restore point** and Custom restore point.

5. Select **Latest restore point**.
1. Select **Latest restore point**.

6. Provide a new server name in the **Restore to new server** field.
1. Provide a new server name in the **Restore to new server** field.

:::image type="content" source="./media/how-to-restore-server-portal/point-in-time-restore-latest.png" alt-text="Earliest restore time":::
:::image type="content" source="./media/how-to-restore-server-portal/point-in-time-restore-latest.png" alt-text="Sreenshot of earliest restore time" lightbox="./media/how-to-restore-server-portal/point-in-time-restore-latest.png":::

7. Click **OK**.

8. A notification will be shown that the restore operation has been initiated.
1. Select **OK**.

1. A notification is shown that the restore operation has been initiated.

## Restore to a fastest restore point

Follow these steps to restore your flexible server using an existing full backup as the fastest restore point.
Follow these steps to restore your flexible server using an existing full backup as the fastest restore point.

1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.

1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.
1. Select **Overview** from the left panel.

2. Click **Overview** from the left panel.
1. From the overview page, select **Restore**.

3. From the overview page, click **Restore**.
1. Restore page is shown with an option to choose between Latest restore point, Custom restore point and Fastest Restore Point.

4. Restore page will be shown with an option to choose between Latest restore point, Custom restore point and Fastest Restore Point.
1. Select option **Select fastest restore point (Restore using full backup)**.

5. Select option **Select fastest restore point (Restore using full backup)**.
1. Select the desired full backup from the **Fastest Restore Point (UTC)** dropdown list.

6. Select the desired full backup from the **Fastest Restore Point (UTC)** drop down list .

:::image type="content" source="./media/how-to-restore-server-portal/fastest-restore-point.png" alt-text="Fastest Restore Point":::
:::image type="content" source="./media/how-to-restore-server-portal/fastest-restore-point.png" alt-text="Sreenshot of Fastest Restore Point" lightbox="./media/how-to-restore-server-portal/fastest-restore-point.png":::

7. Provide a new server name in the **Restore to new server** field.
1. Provide a new server name in the **Restore to new server** field.

8. Click **Review + Create**.
1. Select **Review + Create**.

9. Post clicking **Create**, a notification will be shown that the restore operation has been initiated.
1. Post selecting **Create**, a notification is shown that the restore operation has been initiated.

## Restore from a full backup through the Backup and Restore blade
## Restore from a full backup through the Backup and Restore page

Follow these steps to restore your flexible server using an existing full backup.
Follow these steps to restore your flexible server using an existing full backup.

1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.
1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.

2. Click **Backup and Restore** from the left panel.
1. Select **Backup and Restore** from the left panel.

3. View Available Backups page will be shown with the option to restore from available full automated backups and on-demand backups taken for the server within the retention period.
1. View Available Backups page is shown with the option to restore from available full automated backups and on-demand backups taken for the server within the retention period.

4. Select the desired full backup from the list by clicking on corresponding **Restore** action.

:::image type="content" source="./media/how-to-restore-server-portal/view-available-backups.png" alt-text="View Available Backups":::
1. Select the desired full backup from the list by selecting on corresponding **Restore** action.

5. Restore page will be shown with the Fastest Restore Point option selected by default and the desired full backup timestamp selected on the View Available backups page.
:::image type="content" source="./media/how-to-restore-server-portal/view-available-backups.png" alt-text="Sreenshot of view Available Backups" lightbox="./media/how-to-restore-server-portal/view-available-backups.png":::

6. Provide a new server name in the **Restore to new server** field.
1. Restore page is shown with the Fastest Restore Point option selected by default and the desired full backup timestamp selected on the View Available backups page.

7. Click **Review + Create**.
1. Provide a new server name in the **Restore to new server** field.

8. Post clicking **Create**, a notification will be shown that the restore operation has been initiated.
1. Select **Review + Create**.

1. Post selecting **Create**, a notification is shown that the restore operation has been initiated.

## Geo-restore to latest restore point

1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.

2. Click **Overview** from the left panel.
1. Select **Overview** from the left panel.

3. From the overview page, click **Restore**.
1. From the overview page, select **Restore**.

4. Restore page will be shown with an option to choose **Geo-redundant restore**. If you have configured your server for geographically redundant backups, the server can be restored to the corresponding Azure paired region and the geo-redundant restore option can be enabled. Geo-redundant restore option restores the server to Latest UTC Now timestamp and hence after selection of Geo-redundant restore, the point-in-time restore options cannot be selected simultaneously.
1. Restore page is shown with an option to choose **Geo-redundant restore**. If you have configured your server for geographically redundant backups, the server can be restored to the corresponding Azure paired region and the geo-redundant restore option can be enabled. Geo-redundant restore option restores the server to Latest UTC Now timestamp and hence after selection of Geo-redundant restore, the point-in-time restore options can't be selected simultaneously.

:::image type="content" source="./media/how-to-restore-server-portal/georestore-flex.png" alt-text="Geo-restore option":::
:::image type="content" source="./media/how-to-restore-server-portal/georestore-flex.png" alt-text="Sreenshot of Geo-restore option" lightbox="./media/how-to-restore-server-portal/georestore-flex.png":::

:::image type="content" source="./media/how-to-restore-server-portal/georestore-enabled-flex.png" alt-text="Enabling Geo-Restore":::
:::image type="content" source="./media/how-to-restore-server-portal/georestore-enabled-flex.png" alt-text="Sreenshot of enabling Geo-Restore" lightbox="./media/how-to-restore-server-portal/georestore-enabled-flex.png":::

1. Provide a new server name in the **Name** field in the Server details section and select the location (paired or any other region).
6. When primary region is down, one cannot create geo-redundant servers in the respective geo-paired region as storage cannot be provisioned in the primary region. One must wait for the primary region to be up to provision geo-redundant servers in the geo-paired region. With the primary region down one can still geo-restore the source server to the geo-paired region by disabling the geo-redundancy option in the Compute + Storage Configure Server settings in the restore portal experience and restore as a locally redundant server to ensure business continuity.
1. Provide a new server name in the **Name** field in the Server details section.

:::image type="content" source="./media/how-to-restore-server-portal/georestore-region-down-1.png" alt-text="Compute + Storage window":::
1. When primary region is down, one can't create geo-redundant servers in the respective geo-paired region as storage can't be provisioned in the primary region. One must wait for the primary region to be up to provision geo-redundant servers in the geo-paired region. With the primary region down one can still geo-restore the source server to the geo-paired region by disabling the geo-redundancy option in the Compute + Storage Configure Server settings in the restore portal experience and restore as a locally redundant server to ensure business continuity.
:::image type="content" source="./media/how-to-restore-server-portal/georestore-region-down-1.png" alt-text="Sreenshot of Compute + Storage window" lightbox="./media/how-to-restore-server-portal/georestore-region-down-1.png":::

:::image type="content" source="./media/how-to-restore-server-portal/georestore-region-down-2.png" alt-text="Disabling Geo-Redundancy":::
:::image type="content" source="./media/how-to-restore-server-portal/georestore-region-down-2.png" alt-text="Sreenshot of Disabling Geo-Redundancy" lightbox="./media/how-to-restore-server-portal/georestore-region-down-2.png":::

:::image type="content" source="./media/how-to-restore-server-portal/georestore-region-down-3.png" alt-text="Restoring as Locally redundant server":::
:::image type="content" source="./media/how-to-restore-server-portal/georestore-region-down-3.png" alt-text="Sreenshot of Restoring as Locally redundant server" lightbox="./media/how-to-restore-server-portal/georestore-region-down-3.png":::

7. Select **Review + Create** to review your selections.
1. Select **Review + Create** to review your selections.

8. A notification will be shown that the restore operation has been initiated. This operation may take a few minutes.
1. A notification is shown that the restore operation has been initiated. This operation may take a few minutes.

The new server created by geo-restore has the same server admin login name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's Overview page. Additionally during a geo-restore, **Networking** settings such as virtual network settings and firewall rules can be configured as described in the below section.
The new server created by geo-restore has the same server admin sign-in name and password that was valid for the existing server at the time the restore was initiated. The password can be changed from the new server's Overview page. Additionally during a geo-restore, **Networking** settings such as virtual network settings and firewall rules can be configured as described in the below section.

## Using restore to move a server from Public access to Private access
## Use restore to move a server from Public access to Private access

Follow these steps to restore your flexible server using an earliest existing backup.

1. In the [Azure portal](https://portal.azure.com/), choose your flexible server that you want to restore the backup from.

2. From the overview page, click **Restore**.
1. From the overview page, select **Restore**.

3. Restore page will be shown with an option to choose between Geo-restore or Point-in-time restore options.
1. Restore page is shown with an option to choose between Geo-restore or Point-in-time restore options.

4. Choose either **Geo-restore** or a **Point-in-time restore** option.
1. Choose either **Geo-restore** or a **Point-in-time restore** option.

5. Provide a new server name in the **Restore to new server** field.
1. Provide a new server name in the **Restore to new server** field.

:::image type="content" source="./media/how-to-restore-server-portal/point-in-time-restore-private-dns-zone.png" alt-text="view overview":::
:::image type="content" source="./media/how-to-restore-server-portal/point-in-time-restore-private-dns-zone.png" alt-text="Sreenshot of view overview" lightbox="./media/how-to-restore-server-portal/point-in-time-restore-private-dns-zone.png":::

6. Go to the **Networking** tab to configure networking settings.
1. Go to the **Networking** tab to configure networking settings.

7. 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 clicking the *create virtual network* link.
> [!Note]
> Only virtual networks and subnets in the same region and subscription will be listed in the drop down. </br>
> The chosen subnet will be delegated to *Microsoft.DBforMySQL/flexibleServers*. It means that only Azure Database for MySQL - Flexible Servers can use that subnet.</br>
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.
> [!NOTE]
> Only virtual networks and subnets in the same region and subscription is listed in the dropdown list. </br>
> The chosen subnet is delegated to *Microsoft.DBforMySQL/flexibleServers*. It means that only Azure Database for MySQL - Flexible Servers can use that subnet.</br>
:::image type="content" source="./media/how-to-manage-virtual-network-portal/vnet-creation.png" alt-text="Vnet configuration":::
:::image type="content" source="./media/how-to-manage-virtual-network-portal/vnet-creation.png" alt-text="Sreenshot of Vnet configuration" lightbox="./media/how-to-manage-virtual-network-portal/vnet-creation.png":::

8. Create a new or Select an existing **Private DNS Zone**.
> [!NOTE]
1. Create a new or Select an existing **Private DNS Zone**.
> [!NOTE]
> Private DNS zone names must end with `mysql.database.azure.com`. </br>
> If you do not see the option to create a new private dns zone, please enter the server name on the **Basics** tab.</br>
> After the flexible server is deployed to a virtual network and subnet, you cannot move it to Public access (allowed IP addresses).</br>
:::image type="content" source="./media/how-to-manage-virtual-network-portal/private-dns-zone.png" alt-text="dns configuration":::
9. Select **Review + create** to review your flexible server configuration.
10. Select **Create** to provision the server. Provisioning can take a few minutes.

11. A notification will be shown that the restore operation has been initiated.
:::image type="content" source="./media/how-to-manage-virtual-network-portal/private-dns-zone.png" alt-text="Sreenshot of dns configuration" lightbox="./media/how-to-manage-virtual-network-portal/private-dns-zone.png":::
1. Select **Review + create** to review your flexible server configuration.
1. Select **Create** to provision the server. Provisioning can take a few minutes.

1. A notification is shown that the restore operation has been initiated.

## Perform post-restore tasks

After the restore is completed, you should perform the following tasks to get your users and applications back up and running:

- If the new server is meant to replace the original server, redirect clients and client applications to the new server.
- Ensure appropriate VNet rules are in place for users to connect. These rules are not copied over from the original server.
- Ensure appropriate virtual network rules are in place for users to connect. These rules aren't copied over from the original server.
- Ensure appropriate logins and database level permissions are in place.
- Configure alerts as appropriate for the newly restore server.

## Next steps

Learn more about [business continuity](concepts-business-continuity.md)

- Learn more about [business continuity](concepts-business-continuity.md)
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 556bb1d

Please sign in to comment.