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: Dec 08, 2021 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.

Binlog is enabled for RDS by default and uses the row-based logging.

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

If the retention period is set to 0, the binlogs will be deleted once they are synchronized to the standby instance and read replicas from the primary instance and successfully backed up to OBS. If the retention period is longer than 0, the binlogs exceeding the retention period will be deleted.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click in the upper left corner of the page and choose Database > Relational Database Service. 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

    When binlogs are deleted depends on the local retention period you configure on the console.

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