Skip to content

Commit 0f19021

Browse files
committed
Updated docs based on review comments
1 parent 04b65ea commit 0f19021

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed
-85 Bytes
Loading
-100 Bytes
Loading

articles/dms/migrate-azure-mysql-consistent-backup.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ The binlog keeps a record of all the CRUD operations in the source server. The D
5757

5858
:::image type="content" source="media/migrate-azure-mysql-consistent-backup/dms-binlog-status-display.png" alt-text="MySQL to Azure Database for MySQL Data Migration Wizard - Migration complete display binlog status" lightbox="media/migrate-azure-mysql-consistent-backup/dms-binlog-status-display.png":::
5959

60-
This binlog position can be used in conjunction with [Data-in replication](https://docs.microsoft.com/azure/mysql/concepts-data-in-replication) or third-party tools (such as Striim or Attunity) that provide for replaying binlog changes to a different server, if required.
60+
This binlog position can be used in conjunction with [Data-in replication](../mysql/concepts-data-in-replication.md) or third-party tools (such as Striim or Attunity) that provide for replaying binlog changes to a different server, if required.
6161

6262
The binary log is deleted periodically, so the user must take necessary precautions if Change Data Capture (CDC) is used later to migrate the post-migration updates at the source. Configure the **binlog_expire_logs_seconds** parameter on the source server to ensure that binlogs are not purged before the replica commits the changes. If non-zero, binary logs will be purged after **binlog_expire_logs_seconds** seconds. Post successful cut-over, you can reset the value. Users will need to leverage the changes in the binlog to carry out the online migration. Users can take advantage of DMS to provide the initial seeding of the data and then stitch that together with the CDC solution of their choice to implement a minimal downtime migration.
6363

@@ -97,6 +97,6 @@ The migration handles transient connection issues and additional connections are
9797

9898
## Next steps
9999

100-
- Learn more about [Data-in Replication](https://docs.microsoft.com/azure/mysql/concepts-data-in-replication)
100+
- Learn more about [Data-in Replication](../mysql/concepts-data-in-replication.md)
101101

102-
- [Tutorial: Migrate MySQL to Azure Database for MySQL offline using DMS](https://docs.microsoft.com/azure/dms/tutorial-mysql-azure-mysql-offline-portal)
102+
- [Tutorial: Migrate MySQL to Azure Database for MySQL offline using DMS](tutorial-mysql-azure-mysql-offline-portal.md)

0 commit comments

Comments
 (0)