This bug is mostly a duplicate of https://bugs.launchpad.net/bugs/2003866, and is caused by the same underlying issue. The difference though is that they were able to solve the issue by granting the RELOAD privilege to the backup user, as recommended by the error message they reported.
What I'm adding here is that when trying to back up from an AWS RDS MySQL database, even after granting that permission as suggested by that initial error message, it *still* doesn't work: you get the new error message that I reported above, because AWS RDS doesn't allow the 'FLUSH TABLES WITH READ LOCK' no matter what privileges have been granted, even for root/admin accounts.
This bug is mostly a duplicate of https:/ /bugs.launchpad .net/bugs/ 2003866, and is caused by the same underlying issue. The difference though is that they were able to solve the issue by granting the RELOAD privilege to the backup user, as recommended by the error message they reported.
What I'm adding here is that when trying to back up from an AWS RDS MySQL database, even after granting that permission as suggested by that initial error message, it *still* doesn't work: you get the new error message that I reported above, because AWS RDS doesn't allow the 'FLUSH TABLES WITH READ LOCK' no matter what privileges have been granted, even for root/admin accounts.