If you replay any large transactions, a low wait_timeout value can break point-in-time restore processes in Amazon RDS for MySQL. For example, breaks occur if you're performing a large row-based bulk update, insert, or delete and the replay takes longer than wait_timeout. To prevent any disruptions in the PITR process, set the wait_timeout value to "600" (10 minutes) or more. For more information, see the wait_timeout section in Best practices for configuring parameters for Amazon RDS for MySQL.
When row-based binary logging is used, consider setting the binlog_row_image parameter value to "MINIMAL" instead of "FULL". This updated value will reduce the size of the binary logs, minimizing binlog recovery time.
Unless you need a specific binlog format, consider using the MIXED logging format. With mixed logging, statement-based logging is used by default, but the logging mode switches automatically to row-based as needed. This switching can help reduce binlog sizes. For more information about MIXED logging, see Binary logging formats on the MySQL website.
Point-in-time recovery failures
The following scenarios will cause point-in-time recovery to fail: