File Maintenance process for MySQL database logs

We all know that log files are the main reference for restoring database data, so the actual maintenance of MySQL database log files is also very important. When the MySQL database and related log files are used together, you sometimes want to delete/back up the old log files and tell MySQL to start recording in the new files.

This article describes how to enable new log files, including updates and general logs. The method described here also applies to binary logs.

How to use the new update log

If you only use one Update log, you only need to clear the log file, then remove the old Update log file to a backup, and then enable the new update log.

Use the following methods to force the server to enable new MySQL database updates:

 
 

  
  
mysqladmin flush-logs 
 
 

You generally need to provide the following database users in the command line:

 
 

  
  
mysqladmin –u root –p flush-logs  
  
  
mysqladmin refresh  
 
 

You generally need to provide the following database users in the command line:

 
 

  
  
mysqladmin –u root –p refresh 
 
 

If you are using MySQL 3.21 or earlier, you must use mysqladmin refresh.

SQL commands

 
 

  
  
FLUSH LOGS 
 
 

Restart the server

The preceding methods have the following functions:

Close and then open the standard and update record files. If you specify an update record file without an extension, the extension number of the new update record file will be 1 higher than that of the previous file.

 
 

  
  
mysql>FLUSH LOGS; 
 
 

How to use new regular logs

The above method can also force updates to the general MySQL database logs.

To back up General logs, the steps may be complicated:

 
 

  
  
$ cd mysql-data-directory$ mv mysql.log mysql.old$ mysqladmin flush-tables 
 
 

Make a backup and delete "mysql. old ".