Merge pull request #167010 from SudheeshGH/replicapfs

Replica Creation issues updated on Doc

Author: v-ccolin

articles/mysql/concepts-pricing-tiers.md

@@ -98,6 +98,17 @@ General purpose storage v2 is supported in the following Azure regions:
 | West US | :heavy_check_mark: | 
 | West US 2 | :heavy_check_mark: | 
 | West Europe | :heavy_check_mark: | 
+| Central India* | :heavy_check_mark: | 
+| France Central* | :heavy_check_mark: | 
+| UAE North* | :heavy_check_mark: | 
+| South Africa North* | :heavy_check_mark: |
+
+> [!Note] 
+> *Regions where Azure Database for MySQL has General purpose storage v2 in Public Preview <br /> 
+> *For these Azure regions, you will have an option to create server in both General purpose storage v1 and v2. For the servers created with General purpose storage v2 in public preview, following are the limitations, <br /> 
+> * Geo-Redundant Backup will not be supported<br /> 
+> * The replica server should be in the regions which support General purpose storage v2. <br /> 
+	
 
 ### How can I determine which storage type my server is running on?
 

articles/mysql/concepts-read-replicas.md

@@ -45,7 +45,39 @@ You can have a source server in any [Azure Database for MySQL region](https://az
 
 You can create a read replica in any of the following regions, regardless of where your source server is located. The supported universal replica regions include:
 
-Australia East, Australia Southeast, Brazil South, Canada Central, Canada East, Central US, East Asia, East US, East US 2, Japan East, Japan West, Korea Central, Korea South, North Central US, North Europe, South Central US, Southeast Asia, UK South, UK West, West Europe, West US, West US 2, West Central US.
+| Region | Replica availability | 
+| --- | --- | 
+| Australia East | :heavy_check_mark: | 
+| Australia South East | :heavy_check_mark: | 
+| Brazil South | :heavy_check_mark: | 
+| Canada Central | :heavy_check_mark: |
+| Canada East | :heavy_check_mark: |
+| Central US | :heavy_check_mark: | 
+| East US | :heavy_check_mark: | 
+| East US 2 | :heavy_check_mark: |
+| East Asia | :heavy_check_mark: | 
+| Japan East | :heavy_check_mark: | 
+| Japan West | :heavy_check_mark: | 
+| Korea Central | :heavy_check_mark: |
+| Korea South | :heavy_check_mark: |
+| North Europe | :heavy_check_mark: | 
+| North Central US | :heavy_check_mark: | 
+| South Central US | :heavy_check_mark: | 
+| Southeast Asia | :heavy_check_mark: | 
+| UK South | :heavy_check_mark: | 
+| UK West | :heavy_check_mark: | 
+| West Central US | :heavy_check_mark: | 
+| West US | :heavy_check_mark: | 
+| West US 2 | :heavy_check_mark: | 
+| West Europe | :heavy_check_mark: | 
+| Central India* | :heavy_check_mark: | 
+| France Central* | :heavy_check_mark: | 
+| UAE North* | :heavy_check_mark: | 
+| South Africa North* | :heavy_check_mark: |
+
+> [!Note] 
+> *Regions where Azure Database for MySQL has General purpose storage v2 in Public Preview  <br /> 
+> *For these Azure regions, you will have an option to create server in both General purpose storage v1 and v2. For the servers created with General purpose storage v2 in public preview, you are limited to create replica server only in the Azure regions which support General purpose storage v2.
 
 ### Paired regions
 

articles/mysql/howto-read-replicas-cli.md

@@ -57,7 +57,9 @@ az mysql server replica create --name mydemoreplicaserver --source-server mydemo
 > To learn more about which regions you can create a replica in, visit the [read replica concepts article](concepts-read-replicas.md). 
 
 > [!NOTE]
-> Read replicas are created with the same server configuration as the master. The replica server configuration can be changed after it has been created. It is recommended that the replica server's configuration should be kept at equal or greater values than the source to ensure the replica is able to keep up with the master.
+> * The `az mysql server replica create` command has `--sku-name` argument which allows you to specify the sku (`{pricing_tier}_{compute generation}_{vCores}`) while you create a replica using Azure CLI. </br>
+> * The primary server and read replica should be on same pricing tier (General Purpose or Memory Optimized). </br>
+> * The replica server configuration can also be changed after it has been created. It is recommended that the replica server's configuration should be kept at equal or greater values than the source to ensure the replica is able to keep up with the master.
 
 
 ### List replicas for a source server
@@ -177,6 +179,14 @@ When you delete a source server, replication to all read replicas is stopped. Th
 DELETE https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMySQL/servers/{serverName}?api-version=2017-12-01
 ```
 
+### Known issue
+
+There are two generations of storage which the servers in General Purpose and Memory Optimized tier use, General purpose storage v1 (Supports up to 4-TB) & General purpose storage v2 (Supports up to 16-TB storage).
+Source server and the replica server should have same storage type. As [General purpose storage v2](./concepts-pricing-tiers.md#general-purpose-storage-v2-supports-up-to-16-tb-storage) is not available in all regions, please make sure you choose the correct replica region while you use location with the CLI or REST API for read replica creation. On how to identify the storage type of your source server refer to link [How can I determine which storage type my server is running on](./concepts-pricing-tiers.md#how-can-i-determine-which-storage-type-my-server-is-running-on). 
+
+If you choose a region where you cannot create a read replica for your source server, you will encounter the issue where the deployment will keep running as shown in the figure below and then will timeout with the error *“The resource provision operation did not complete within the allowed timeout period.”*
+
+[ :::image type="content" source="media/howto-read-replicas-cli/replcia-cli-known-issue.png" alt-text="Read replica cli error.":::](media/howto-read-replicas-cli/replcia-cli-known-issue.png#lightbox)
 
 ## Next steps
 

articles/mysql/howto-read-replicas-powershell.md

@@ -74,8 +74,8 @@ Get-AzMySqlServer -Name mrdemoserver -ResourceGroupName myresourcegroup |
   New-AzMySqlReplica -Name mydemoreplicaserver -ResourceGroupName myresourcegroup -Location westus
 ```
 
-To learn more about which regions you can create a replica in, visit the
-[read replica concepts article](concepts-read-replicas.md).
+> [!NOTE]
+> To learn more about which regions you can create a replica in, visit the [read replica concepts article](concepts-read-replicas.md). 
 
 By default, read replicas are created with the same server configuration as the source unless the
 **Sku** parameter is specified.
@@ -119,6 +119,16 @@ To delete a source server, you can run the `Remove-AzMySqlServer` cmdlet.
 Remove-AzMySqlServer -Name mydemoserver -ResourceGroupName myresourcegroup
 ```
 
+### Known Issue
+
+There are two generations of storage which the servers in General Purpose and Memory Optimized tier use, General purpose storage v1 (Supports up to 4-TB) & General purpose storage v2 (Supports up to 16-TB storage).
+Source server and the replica server should have same storage type. As [General purpose storage v2](./concepts-pricing-tiers.md#general-purpose-storage-v2-supports-up-to-16-tb-storage) is not available in all regions, please make sure you choose the correct replica region while you use location with the PowerShell for read replica creation. On how to identify the storage type of your source server refer to link [How can I determine which storage type my server is running on](./concepts-pricing-tiers.md#how-can-i-determine-which-storage-type-my-server-is-running-on). 
+
+If you choose a region where you cannot create a read replica for your source server, you will encounter the issue where the deployment will keep running as shown in the figure below and then will timeout with the error *“The resource provision operation did not complete within the allowed timeout period.”*
+
+[ :::image type="content" source="media/howto-read-replicas-powershell/replcia-ps-known-issue.png" alt-text="Read replica cli error":::](media/howto-read-replicas-powershell/replcia-ps-known-issue.png#lightbox)
+
+
 ## Next steps
 
 > [!div class="nextstepaction"]