Subscribe

MySQL-Replication crashing after Backup

[ Edited ]

Hello,

 

we are using SnapCreator Framework 4.1.0. Now we want to implement a MySQL-Backup (Master-Slave).  After taking a backup of the master the replication of mysql 5.6 is crashing.

 

Log-File MySQL-Slave

 

2015-01-28 10:38:01 4236 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'could not find next log; the first event 'mysqlbin.000014' at 228369668, the last event read from 'E:\mysql_logs\mysqlbin.000015' at 120, the last byte read from 'E:\mysql_logs\mysqlbin.000015' at 120.', Error_code: 1236
2015-01-28 10:38:01 4236 [Note] Slave I/O thread exiting, read up to log 'mysqlbin.000015', position 120

 SHOW SLAVE STATUS output

 

Slave_IO_Running: No, Slave_SQL_Running: Yes

 

The mysqlbin.000015 was gone after the backup. There is only a mysql.000001 file on the master. What command is the framework using to quiesce the databases?

 

In the Backup-Job Master-Slave is set to YES.

 

Hope you can help me to get backup to work. Thank you.

 

 

 

 

 

 

Re: MySQL-Replication crashing after Backup

I think following command is causing the problem "RESET MASTER". I found this command in the debug log of the agent.

 

 

RESET MASTER:

This statement is for use only when the master is started for the first time, and should never be used if any slaves are actively replicating from the binary log. The statement PURGE BINARY LOGS is intended for use in active replication.

 

Is there a developer who can check if its possible to replace this command?