MySQL

Enable binary logging

Edit your MySQL configuration file (my.cnf or my.ini):

[mysqld]
# Server identification (must be unique in your infrastructure)
server-id = 223344

# Binary logging (required)
log_bin = mysql-bin
binlog_format = ROW
binlog_row_image = FULL
binlog_row_metadata = FULL

# GTID (recommended, not required)
gtid_mode = ON
enforce_gtid_consistency = ON

# Binary log retention (3 days)
binlog_expire_logs_seconds = 259200

Create a dedicated user for replication

Connect to MySQL as a privileged user and run:

CREATE USER 'supermetal_user'@'%' IDENTIFIED BY 'strong-password';
GRANT SELECT, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'supermetal_user'@'%';
FLUSH PRIVILEGES;

Verify configuration

SHOW VARIABLES LIKE 'log_bin';
SHOW VARIABLES LIKE 'binlog_format';
SHOW VARIABLES LIKE 'binlog_row_image';
SHOW VARIABLES LIKE 'binlog_row_metadata';
SHOW VARIABLES LIKE 'server_id';
SHOW VARIABLES LIKE 'gtid_mode';

Required values:

• log_bin: ON
• binlog_format: ROW
• binlog_row_image: FULL
• binlog_row_metadata: FULL
• server_id: a non zero value

GTID values (if enabled):

• gtid_mode: ON
• enforce_gtid_consistency: ON

If gtid_mode is OFF, Supermetal uses file+position replication automatically.

Create a parameter group

1. In the AWS RDS console, navigate to "Parameter groups"
2. Click "Create parameter group"
3. Select the MySQL engine and version that matches your RDS instance
4. Enter a name and description (e.g., "supermetal-cdc-params")
5. Click "Create"
6. Select the newly created parameter group and modify the following parameters:
   • binlog_format: ROW
   • binlog_row_image: FULL
   • binlog_row_metadata: FULL
   • gtid-mode: ON (recommended, not required)
   • enforce_gtid_consistency: ON (only if gtid-mode is ON)

Apply the parameter group to your RDS instance

1. Navigate to your RDS instances and select your MySQL instance
2. Click "Modify"
3. Under "Additional configuration", select the parameter group you created
4. Choose "Apply immediately" or schedule for your next maintenance window
5. Click "Continue" and confirm the changes

Set the binary log retention period

Connect to your RDS MySQL instance and run:

CALL mysql.rds_set_configuration('binlog retention hours', 72);

Create a user for replication

CREATE USER 'supermetal_user'@'%' IDENTIFIED BY 'strong-password';
GRANT SELECT, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'supermetal_user'@'%';
FLUSH PRIVILEGES;

Configure server parameters

1. In the Azure portal, navigate to your MySQL server resource
2. Select "Server parameters" under the Settings section
3. Find and set the following parameters:
   • binlog_format: ROW
   • binlog_row_image: FULL
   • binlog_row_metadata: FULL
   • gtid_mode: ON (recommended, not required)
   • enforce_gtid_consistency: ON (only if gtid_mode is ON)
4. Click "Save" to apply the changes
5. Restart your Azure Database for MySQL server if prompted

Create a user for replication

Connect to your Azure MySQL instance and run:

CREATE USER 'supermetal_user'@'%' IDENTIFIED BY 'strong-password';
GRANT SELECT, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'supermetal_user'@'%';
FLUSH PRIVILEGES;