Merge pull request #194572 from aditivgupta/moveregions

Move regions doc

Author: v-regandowner

articles/mysql/flexible-server/how-to-move-regions.md

@@ -0,0 +1,75 @@
+---
+title: Move Azure regions - Azure portal - Azure Database for MySQL Flexible server
+description: Move an Azure Database for MySQL Flexible server from one Azure region to another using the Azure portal.
+author: aditivgupta
+ms.author: adig
+ms.service: mysql
+ms.topic: how-to
+ms.custom: subject-moving-resources
+ms.date: 04/08/2022
+#Customer intent: As an Azure service administrator, I want to move my service resources to another Azure region.
+---
+
+# Move an Azure Database for MySQL flexible server to another region by using the Azure portal
+
+There are various scenarios for moving an existing Azure Database for MySQL flexible server from one region to another. For example, you might want to move a production server to another region as part of your disaster recovery planning.
+
+You can use Azure Database for MySQL flexible server's [geo-restore](concepts-backup-restore.md#geo-restore) feature to complete the move to another region. To do so, first ensure geo-redundancy is enabled for your flexible server. Next, trigger geo-restore for your geo-redundant server and move your server to the geo-paired region.
+
+> [!NOTE]
+> This article focuses on moving your server to a different region. If you want to move your server to a different resource group or subscription, refer to the [move](../../azure-resource-manager/management/move-resource-group-and-subscription.md) article.
+
+## Prerequisites
+
+- Ensure the source server has geo-redundancy enabled. You can enable geo-redundancy post server-create for locally redundant or same-zone redundant servers. Currently, for a Zone-redundant High Availability server geo-redundancy can only be enabled/disabled at server create time.
+
+- Make sure that your Azure Database for MySQL source flexible server is deployed in the Azure region that you want to move from.
+
+## Move
+
+To move the Azure Database for MySQL flexible server to the geo-paired region using the Azure portal, use the following steps:
+
+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.
+
+3. From the overview page, click **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.
+
+   :::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-enabled-flex.png" alt-text="Enabling Geo-Restore":::
+
+5. Provide a new server name in the **Name** field in the Server details section.
+
+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.
+
+   :::image type="content" source="./media/how-to-restore-server-portal/georestore-region-down-1.png" alt-text="Compute + Storage window":::
+
+   :::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-3.png" alt-text="Restoring as Locally redundant server":::
+
+7. 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.
+
+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.
+
+## Clean up source server
+
+You may want to delete the source Azure Database for MySQL flexible server. To do so, use the following steps:
+
+1. Once the replica has been created, locate and select your Azure Database for MySQL source flexible server.
+1. In the **Overview** window, select **Delete**.
+1. Type in the name of the source server to confirm you want to delete.
+1. Select **Delete**.
+
+## Next steps
+
+In this tutorial, you moved an Azure Database for MySQL flexible server from one region to another by using the Azure portal and then cleaned up the unneeded source resources.
+
+- Learn more about [geo-restore](concepts-backup-restore.md#geo-restore)
+- Learn more about [Azure paired regions](overview.md#azure-regions) supported for Azure Database for MySQL flexible server
+- Learn more about [business continuity](concepts-business-continuity.md) options

articles/mysql/flexible-server/index.yml

@@ -64,6 +64,8 @@ landingContent:
             url: how-to-stop-start-server-portal.md
           - text: Schedule maintenance
             url: how-to-maintenance-portal.md
+          - text: Move servers between regions
+            url: how-to-move-regions.md
 
 # Card
   - title: Business continuity