Bobcares

How to purge MySQL binlogs

by | May 14, 2022

Purge MySQL binlogs like a pro with a little guidance from our in-house experts. 

At Bobcares, we offer solutions for every query, big and small, as a part of our MySQL Support Services.

Let’s take a look at how our MySQL Support Team is ready to help customers understand more about purging MySQL binlogs.

How to purge MySQL binlogs

The binary logs or MySQL binlogs can be described as a set of files consisting of information about data modifications by the MySQL server. In other words, the log contains binary log files as well as an index file.

purge MySQL binlogs

We can delete all binary log files with the help of the following statement:

PURGE { BINARY | MASTER } LOGS { 
 TO 'log_name' 
 | BEFORE datetime_expr 
}

The MySQL binlog files prior to the file name or date are deleted.

Here are a few examples of how to use the statement:

PURGE BINARY LOGS TO 'mariadb-bin.000063';
PURGE BINARY LOGS BEFORE '2021-04-16';
PURGE BINARY LOGS BEFORE '2022-04-12 07:45:32';

In case the server did not start with the –log-bin option, the PURGE BINARY LOGS have no effect. Additionally, the statement requires BINLOG_ADMIN privilege to function.

Moreover, it is safe to run the purge MySQL binlogs statement which replicas are replicating. For instance, if we have an active replica reading a log file that we are attempting to delete, the statement will not delete that specific MySQL binlog file or the ones after it. In fact, we will get a warning message in this scenario.

According to our MySQL Support Techs, we should not issues the PURGE BINARY LOGS statement if a LOCK INSTANCE FOR BACKUP statement is in place for the instance.

Furthermore, MySQL automatically removes MySQL binlogs files after the expiration period of the binary log. By default, the expiration period is 30 days. However, we can modify this by changing the binlog_expire_logs_seconds system variable value.

[Need assistance with another query? We are available 24/7.]

Conclusion

In a nutshell, our skilled MySQL Support Engineers at Bobcares helped us understand more about purging MySQL binlogs.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF