Is it necessary to enable the Binary Log in MySQL?

ditulis.id

I am currently facing an issue where my server's storage capacity suddenly becomes full due to files generated by the MySQL Binary Log. I have tried using the Log Cleanup tool provided in aaPanel. However, when the binary log files exceed 3GB in size, the Log Cleanup tool fails to delete them completely, leaving residual files behind as shown in the image below.

and the following is if I use the log cleanup application which cannot detect binary log files that have accumulated up to 16GB

Is there a solution to ensure complete cleanup of binary log files and free up HDD space more effectively, aside from using the Log Cleanup tool? Or is there a manual yet safe method to handle this?

Thanks

aaP_hareeshnarayan1982

Removing binlog should be done carefully. They are used for recovery and db replication. If you don't use replication and don't require recovery, then you can check current binlog in mysql shell and then remove the older one. With binlogs you can do Point in time restore in case of a crash.

ditulis.id

aaP_hareeshnarayan1982 thanks for the information, but there is something I am confused about. how do I access the mysql shell?

aaPanel_Kern

Hello,
It is recommended that you make a backup of the server snapshot first and then delete it
Also check the configuration of expire_logs_days

ditulis.id

aaPanel_Kern In expire_logs_days I leave it at 10 days, should I change the time period to be shorter than 10 days?

aaPanel_Kern

Yes, you can try it, the change requires restarting mysql

ditulis.id

aaPanel_Kern ok thanks for the information and help for all the aapanel team