We are using mysql Ver 14.14 Distrib 5.1.73, for redhat-linux-gnu (x86_64) using readline 5.1, CentOS 6.8.
I have inherited a server which has a bunch of mysqld-relay-bin.* files. most of them are old from 2010-2015. In 2016 I implemented a new backup strategy in which i use "mysqldump --single-transaction --flush-logs --master-data=2 --all-databases --delete-master-logs > dump.sql" once for a full backup and then "mysqladmin flush-logs" for incremental backups which creates separate mysql-bin.* files. However this also started creating new mysqld-relay-bin.* files which do not get removed with the Full backup "mysqldump" command above. I read these files have to do with replication, which we aren't using AFAIK. The /etc/my.cnf had "server-id = 1" in it which i commented out but this hasn't helped.
I'm not an expert in mysql so not really sure what these files are for or why they are getting created, or how I could stop them from being created and ultimately delete them.
I have inherited a server which has a bunch of mysqld-relay-bin.* files. most of them are old from 2010-2015. In 2016 I implemented a new backup strategy in which i use "mysqldump --single-transaction --flush-logs --master-data=2 --all-databases --delete-master-logs > dump.sql" once for a full backup and then "mysqladmin flush-logs" for incremental backups which creates separate mysql-bin.* files. However this also started creating new mysqld-relay-bin.* files which do not get removed with the Full backup "mysqldump" command above. I read these files have to do with replication, which we aren't using AFAIK. The /etc/my.cnf had "server-id = 1" in it which i commented out but this hasn't helped.
I'm not an expert in mysql so not really sure what these files are for or why they are getting created, or how I could stop them from being created and ultimately delete them.