Skip to content

Commit fc6fdb8

Browse files
authored
Update concepts-read-replicas.md
1 parent fb647dc commit fc6fdb8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/mysql/concepts-read-replicas.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ However, there are limitations to consider:
5656

5757
If a master server has no existing replica servers, the master will first restart to prepare itself for replication.
5858

59-
When you start the create replica workflow, a blank Azure Database for MySQL server is created. The new server is filled with the data that was on the master server. The creation time depends on the amount of data on the master and the time since the last weekly full backup. The time can range from a few minutes to several hours.
59+
When you start the create replica workflow, a blank Azure Database for MySQL server is created. The new server is filled with the data that was on the master server. The creation time depends on the amount of data on the master and the time since the last weekly full backup. The time can range from a few minutes to several hours.The replica server is always created in the same resource group and same subscription as the master server. If you want to create a replica server to a different resource group or different subscription, you can [move the replica server](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription) after creation.
6060

6161
Every replica is enabled for storage [auto-grow](concepts-pricing-tiers.md#storage-auto-grow). The auto-grow feature allows the replica to keep up with the data replicated to it, and prevent an interruption in replication caused by out-of-storage errors.
6262

0 commit comments

Comments
 (0)