Skip to content

Commit 7a91de7

Browse files
authored
Merge pull request #112202 from ajlam/replicainherit
Remove vnet from replica docs
2 parents d6da47a + bab52d5 commit 7a91de7

File tree

2 files changed

+6
-7
lines changed

2 files changed

+6
-7
lines changed

articles/mariadb/concepts-read-replicas.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mariadb
77
ms.topic: conceptual
8-
ms.date: 3/18/2020
8+
ms.date: 04/21/2020
99
---
1010

1111
# Read replicas in Azure Database for MariaDB
@@ -68,7 +68,7 @@ Learn how to [create a read replica in the Azure portal](howto-read-replicas-por
6868

6969
## Connect to a replica
7070

71-
At creation, a replica inherits the firewall rules or VNet service endpoint of the master server. Afterwards, these rules are independent from the the master server.
71+
At creation, a replica inherits the firewall rules of the master server. Afterwards, these rules are independent from the the master server.
7272

7373
The replica inherits the admin account from the master server. All user accounts on the master server are replicated to the read replicas. You can only connect to a read replica by using the user accounts that are available on the master server.
7474

@@ -121,7 +121,7 @@ A replica is created by using the same server configuration as the master. After
121121
> [!IMPORTANT]
122122
> Before a master server configuration is updated to new values, update the replica configuration to equal or greater values. This action ensures the replica can keep up with any changes made to the master.
123123
124-
Firewall rules, virtual network rules, and parameter settings are inherited from the master server to the replica when the replica is created. Afterwards, the replica's rules are independent.
124+
Firewall rules and parameter settings are inherited from the master server to the replica when the replica is created. Afterwards, the replica's rules are independent.
125125

126126
### Stopped replicas
127127

articles/mysql/concepts-read-replicas.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ajlam
55
ms.author: andrela
66
ms.service: mysql
77
ms.topic: conceptual
8-
ms.date: 01/16/2020
8+
ms.date: 04/21/2020
99
---
1010

1111
# Read replicas in Azure Database for MySQL
@@ -40,7 +40,6 @@ Australia East, Australia Southeast, Central US, East Asia, East US, East US 2,
4040

4141
*West US 2 is temporarily unavailable as a cross region replica location.
4242

43-
4443
### Paired regions
4544
In addition to the universal replica regions, you can create a read replica in the Azure paired region of your master server. If you don't know your region's pair, you can learn more from the [Azure Paired Regions article](../best-practices-availability-paired-regions.md).
4645

@@ -66,7 +65,7 @@ Learn how to [create a read replica in the Azure portal](howto-read-replicas-por
6665

6766
## Connect to a replica
6867

69-
At creation, a replica inherits the firewall rules or VNet service endpoint of the master server. Afterwards, these rules are independent from the the master server.
68+
At creation, a replica inherits the firewall rules of the master server. Afterwards, these rules are independent from the the master server.
7069

7170
The replica inherits the admin account from the master server. All user accounts on the master server are replicated to the read replicas. You can only connect to a read replica by using the user accounts that are available on the master server.
7271

@@ -119,7 +118,7 @@ A replica is created by using the same server configuration as the master. After
119118
> [!IMPORTANT]
120119
> Before a master server configuration is updated to new values, update the replica configuration to equal or greater values. This action ensures the replica can keep up with any changes made to the master.
121120
122-
Firewall rules, virtual network rules, and parameter settings are inherited from the master server to the replica when the replica is created. Afterwards, the replica's rules are independent.
121+
Firewall rules and parameter settings are inherited from the master server to the replica when the replica is created. Afterwards, the replica's rules are independent.
123122

124123
### Stopped replicas
125124

0 commit comments

Comments
 (0)