1 Answer
- Newest
- Most votes
- Most comments
0
Hi
Here is the related question answered https://repost.aws/questions/QUF82SbQh6SUi5yT4Ito-BLw/why-don-t-i-get-en-event-with-binlog-information-when-i-create-a-snapshot
Binlogs info Link: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql-stored-proc-configuring.html
binlog retention hours
The binlog retention hours parameter is used to specify the number of hours to retain binary log files. Amazon RDS normally purges a binary log as soon as possible, but the binary log might still be required for replication with a MySQL database external to RDS.
The default value of binlog retention hours is NULL. For RDS for MySQL, NULL means binary logs aren't retained (0 hours).
To specify the number of hours to retain binary logs on a DB instance, use the mysql.rds_set_configuration stored procedure and specify a period with enough time for replication to occur, as shown in the following example.
call mysql.rds_set_configuration('binlog retention hours', 24);
Note
You can't use the value 0 for binlog retention hours.
For MySQL DB instances, the maximum binlog retention hours value is 168 (7 days).After you set the retention period, monitor storage usage for the DB instance to make sure that the retained binary logs don't take up too much storage.
Even if you set a
binlog retention period
, those** logs won't be captured in an RDS snapshot**. Snapshots are full backups at a specific point in time, excluding binlogs which track ongoing changes.
answered 12 days ago
Relevant content
- asked 3 years ago
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago