Help Center > > User Guide> Working with RDS for MySQL> Backups and Restorations> Setting a Local Retention Period for MySQL Binlogs

Setting a Local Retention Period for MySQL Binlogs

Updated at: Mar 17, 2020 GMT+08:00

Scenarios

RDS for MySQL deletes local binlogs after they are backed up to OBS. You can set the local retention period for binlogs as required to fully utilize the instance space.

Binlogs can be retained from 0 to 168 (7x24) hours locally.

The rules for deleting local binlogs are as follows:

  1. All local binlogs will be deleted after they are successfully backed up.
  2. The binlogs used for replication between primary DB instances and standby DB instances or read replicas are not deleted, even when the retention period is set to 0.
  3. If the local space usage exceeds 80%, the system ignores the local retention period configured for binlogs and deletes all the binlogs that have been successfully backed up when the local space usage exceeds 90%.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click RDS. The RDS console is displayed.
  4. On the Instance Management page, click the target DB instance.
  5. In the navigation pane on the left, choose Backups & Restorations. On the Binlog Backups page, click Set Binlog Retention Period.
  6. In the displayed dialog box, set the local retention period and click OK.

    Figure 1 Setting the binlog retention period

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel