Page History

Binary log files (often referred to as binlogs) in MySQL are a record of all changes made to the database. They are essential for replication, backups, and recovery purposes. Binlogs track events such as:

• Data modifications (e.g., INSERT, UPDATE, DELETE statements)
• Table and database schema changes (e.g., CREATE, ALTER statements)

MySQL uses binlogs to propagate changes from a master database to one or more slave databases in a replication setup. The slaves read and apply the binlogs from the master to stay synchronized.

Over time the the amount of bin log files increase and therefore so does the size of the file they are stored in.  This will take up hard drive space plus, this will significantly slow the process if you are cloning the system as the more bin log files there are, the more that have to be copied during the cloning process.

Therefore there is some house keeping that needs to be done to ensure the older bin log files get deleted.

• expire_logs_days
  • You can control how long binary logs are kept by setting the expire_logs_days parameter in the
das.ini
• • MySQL configuration file
  • To do this go to  C:\Program Files\Deepnet DualShield\mysql
  • Edit the das.ini file in elevated
notepad
• • Notepad or
note
• • Notepad++
  • Add an entry
under
• • under mysqld for example expire_logs_days = 30

• • This will ensure that logs over 30 days old will be deleted.  You can set the amount of day but we recommend at least 30.