Skip to content

Commit 1811310

Browse files
committed
fix numbering
1 parent 73136b1 commit 1811310

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

articles/mariadb/howto-data-in-replication.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This article describes how to set up Data-in Replication in Azure Database for M
1414

1515
To create a replica in the Azure Database for MariaDB service, Data-in Replication synchronizes data from a master MariaDB server on-premises, in virtual machines (VMs), or in cloud database services.
1616

17-
Review the [limitations and requirements](concepts-data-in-replication.md#limitations-and-considerations) of Data-in replication prior to performing the steps in this article.
17+
Review the [limitations and requirements](concepts-data-in-replication.md#limitations-and-considerations) of Data-in replication before performing the steps in this article.
1818

1919
> [!NOTE]
2020
> If your master server is version 10.2 or newer, we recommend that you set up Data-in Replication by using [Global Transaction ID](https://mariadb.com/kb/en/library/gtid/).
@@ -112,7 +112,7 @@ The following steps prepare and configure the MariaDB server hosted on-premises,
112112
![Replication Slave](./media/howto-data-in-replication/replicationslave.png)
113113
114114
115-
4. Set the master server to read-only mode.
115+
5. Set the master server to read-only mode.
116116
117117
Before you dump a database, the server must be placed in read-only mode. While in read-only mode, the master can't process any write transactions. To help avoid business impact, schedule the read-only window during an off-peak time.
118118

@@ -121,7 +121,7 @@ The following steps prepare and configure the MariaDB server hosted on-premises,
121121
SET GLOBAL read_only = ON;
122122
```
123123

124-
5. Get the current binary log file name and offset.
124+
6. Get the current binary log file name and offset.
125125

126126
To determine the current binary log file name and offset, run the command [`show master status`](https://mariadb.com/kb/en/library/show-master-status/).
127127

@@ -134,7 +134,7 @@ The following steps prepare and configure the MariaDB server hosted on-premises,
134134

135135
Note the binary file name, because it'll be used in later steps.
136136
137-
6. Get the GTID position (optional, needed for replication with GTID).
137+
7. Get the GTID position (optional, needed for replication with GTID).
138138
139139
Run the function [`BINLOG_GTID_POS`](https://mariadb.com/kb/en/library/binlog_gtid_pos/) to get the GTID position for the corresponding binlog file name and offset.
140140

articles/mysql/howto-data-in-replication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This article describes how to set up Data-in Replication in Azure Database for M
1414

1515
To create a replica in the Azure Database for MySQL service, Data-in Replication synchronizes data from a master MySQL server on-premises, in virtual machines (VMs), or in cloud database services.
1616

17-
Review the [limitations and requirements](concepts-data-in-replication.md#limitations-and-considerations) of Data-in replication prior to performing the steps in this article.
17+
Review the [limitations and requirements](concepts-data-in-replication.md#limitations-and-considerations) of Data-in replication before performing the steps in this article.
1818

1919
## Create a MySQL server to be used as replica
2020

0 commit comments

Comments
 (0)