Restoration of MySQL replication + integration with Power BI

Task Description

It is necessary to restore and correctly configure MySQL/MariaDB (GTID) replication between two servers:

• Master (CRM OneBox) →

• Slave (server for Power BI).

The current replication has broken with the error:
Fatal Error 1236 “GTID state not found… binlog purged”
It is necessary to completely reinstall the replication and configure it for stable operation.

What Needs to Be Done

1. Restoration of Replication

• Preparation of the master: binlog configuration, GTID, creating a user for replication.

• Creating a current backup.

• Preparation of the slave: importing the backup, configuring CHANGE MASTER.

• Starting and checking replication (IO/SQL threads, Seconds_behind_master).

2. Ensuring Reliability

• Configure binlog storage for at least 72 hours.

• Set up automatic recovery after a reboot.

• Check the stability of the connection and MySQL parameters.

• Provide recommendations for monitoring (Telegram/e-mail alerts).

3. Integration with Power BI

• Configure the correct connection of Power BI to the slave.

• Check CRM tables (users, shoporder, shopproduct, financepayment, etc.).

• Ensure correct data updates.

4. Documentation (brief)

• How to check the state of replication.

• What to do in case of failures.

• Maintenance recommendations.

Access

We provide:

• 2 servers (AlmaLinux 8 / RockyLinux 8).

• SSH access.

• Port 3306 is open between the servers.

Final Result

• Working and stable MySQL replication.

• No errors (IO/SQL Running = Yes).

• Power BI receives up-to-date data.

• Replication survives reboots/network failures.

• Configured binlog window (minimum 72 hours).

• Provided brief instructions.

Please indicate in your response

• Your experience with MySQL replication / GTID.

• Estimated time for completion.